ReleaseEngineering/PuppetAgain/Modules/packages: Difference between revisions

ReleaseEngineering/PuppetAgain/Modules/packages (view source)

739 bytes removed , 2 April 2013

canmove, Confirmed users

1,394

edits

@@ Line 43: / Line 43: @@
 This define automatically calculates the DMG path and uses the puppet pkgdmg provider to install it.
-In cases where a DMG is publicly available, a comment in the manifest file should indicate the source.  In the more common case where a DMG must be built by hand, a shell script named ''$pkg-dmg.sh'' that builds the DMG should be included next to the manifest file, e.g., ''modules/packages/manifests/wget-dmg.sh''.  This allows others to see changes from version to version of the DMG via 'hg diff', and also records the origin of the DMG so others can upgrade it.
+See [[ReleaseEngineering/PuppetAgain/Packages#Darwin]] for details on installing and creating Darwin packages.
-Since most software is not available in a pre-made DMG, we often find ourselves building DMGs for software like wget.  If the software is not customized or patched, then the manifest and shell script should be in ''modules/packages/manifests''.  If the package is customized or patched, it should be in the ''mozilla'' subdirectory, as described below for "Mozilla-Custom Packages".
 = Packages =