canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain (view source)
Revision as of 16:31, 23 July 2012
, 23 July 2012→Packages
| Line 41: | Line 41: | ||
== Packages == | == Packages == | ||
Remember that we're running puppet on multiple operating systems. If a new package is only required on one operating system, include a ''case $operatingsystem'' and call ''fail()'' in the default branch, so that it will fail loudly if the class is applied on another operating system. If a utility is installed by default on some operating systems, include a clause in the ''case'' with a comment indicating that. | Remember that we're running puppet on multiple operating systems. If a new package is only required on one operating system, include a ''case $operatingsystem'' and call ''fail()'' in the default branch, so that it will fail loudly if the class is applied on another operating system. If a utility is installed by default on some operating systems, include a clause in the ''case'' with a comment indicating that. | ||
=== DMGs === | |||
Every DMG's provenance should be documented somehow in the puppet hg repository. For publicly available DMGs, this can be described in the $package.pp file. Otherwise, add a $package-dmg.sh script that builds the DMG from its prerequisites. See [[ReleaseEngineering/PuppetAgain/HowTo/Build_DMGs]]. | |||
=== Custom Packages === | === Custom Packages === | ||