Issue #17438 has been updated by eric sorenson. Status changed from Unreviewed to Needs More Information Assignee set to C L
Hi C L - thanks for the feature request and problem statement. I either don't understand or don't agree with this part: <blockquote> To deploy changes or re-compiles of such software requires atleast two puppet runs – the first run to remove the software and the second run to install the package again. Often this is not convenient, especially when there are dependencies on the package resource. Likewise, changing the version number of the software just to force a software update is problematic as it has the potential to interfere/conflict with the version numbering of the software distribution itself. </blockquote> This is exactly what the 'release' field in RPM and 'debian.version' in DPKG are for (just to name the packaging systems I'm most familiar with, I think others have a similar field), to indicate a change in the packaging/local release without affecting the upstream version number. The other conditions you describe also seem to fall under the normal mechanisms of software packaging upgrades, so I don't see a general need for `refresh` in the way you describe. Can you let me know if I have misunderstood your proposal? If you want, write some pseudocode as if Puppet already supported the syntax/behaviour you want and explain what it should do. I've put this ticket's status into "Needs more Information" and assigned it to you. Please either (a) update it with the information I've requested and re-assign it to me if you need more help, or (b) change the status to "Closed" if you were able to resolve the issue on your own. ---------------------------------------- Feature #17438: Refresh support for package type https://projects.puppetlabs.com/issues/17438#change-79886 Author: C L Status: Needs More Information Priority: Normal Assignee: C L Category: package Target version: Affected Puppet version: Keywords: package refresh refreshable "static library linking" reinstall Branch: A number of open-source software can be re-compiled to enable additional features, or conversely, disable features (e.g.: sqlite3, subversion, etc). Also some software relies on static linking of other 3rd party libraries (e.g.: apache, postgresql, etc) which requires a recompile when updates to these libraries are available. To deploy changes or re-compiles of such software requires atleast two puppet runs - the first run to remove the software and the second run to install the package again. Often this is not convenient, especially when there are dependencies on the package resource. Likewise, changing the version number of the software just to force a software update is problematic as it has the potential to interfere/conflict with the version numbering of the software distribution itself. Packages should support the refreshable feature where, in response to a refresh event, proceed to de-install and then install the software. With refreshable packages, a file (or in the case of some providers, a response file) could be used to notify a package to reinstall. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
