canmove, Confirmed users
6,441
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 19:18, 4 June 2018
, 4 June 2018→Custom Packages
(Update puppet-lint documentation) |
|||
| Line 151: | Line 151: | ||
If you create a custom package, it should be installed with a class named ''python::mozilla::$package'', so it's clear that it's customized. The package should be documented on the [[ReleaseEngineering/PuppetAgain/Modules/packages|packages module page]]. | If you create a custom package, it should be installed with a class named ''python::mozilla::$package'', so it's clear that it's customized. The package should be documented on the [[ReleaseEngineering/PuppetAgain/Modules/packages|packages module page]]. | ||
For RPMs, the spec file should be checked into build | For RPMs, the spec file should be checked into https://github.com/mozilla/build-puppet in ''modules/packages/manifests/mozilla'', with the same base name as the ''.pp'' file. When you land the changes, the resulting RPM and SRPM should both be added to the appropriate [[ReleaseEngineering/PuppetAgain/Repositories|repository]]. The contents (but maybe not filename) of the spec file embedded in the SRPM should match the checked-in spec file exactly. This system allows (a) review of spec changes and (b) easy rebuilding of custom RPMS. See [[ReleaseEngineering/PuppetAgain/HowTo/Modify a Custom RPM]] for hints on how to build RPMs. | ||
== Strong Dependencies == | == Strong Dependencies == | ||