Actions
User story #4298
closed
Install / upgrade packages
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
At the moment there are two options:
- install only (don't update)
- update only (don't install) -> version x.y.z
I now need to create two directives for the same package. What I would like to see is the option:
- install or update -> version x.y.z
I need package x.y.z and I don't care if it's done with an install or an update.
Updated by Matthieu CERDA almost 11 years ago
- Category set to Techniques
- Status changed from New to 8
- Priority changed from N/A to 3
- Target version set to Ideas (not version specific)
To do this, we would need the addupdate package_policy in CFEngine, which during the last tests proved to be quite buggy.
I think it is time to test that again !
Updated by
Updated by Nicolas CHARLES over 9 years ago
- Related to Bug #6957: You can't do install+update in one shot in the install package technique added
Updated by Jonathan CLARKE over 9 years ago
- Related to Bug #1884: The addupdate target on the package installation Technique is broken. We should enable it again when possible added
Updated by Alexis Mousset over 8 years ago
- Related to User story #8230: Package management issues in Rudder/ncf added
Updated by François ARMAND about 8 years ago
- Status changed from New to Rejected
This is now corrected with: http://www.normation.com/en/blog/2016/10/17/discover-new-package-management-implementation-rudder/
Actions