Changes

The build infrastructure uses two types of rpm's: vanilla and customized for mozilla.Let's clarify the terminology: a "vanilla package" is a package which is publicly available and is used by mozilla without applying any customization. An example of this is the jdk package used for Android builds. A "mozilla custom" package is a package rebuilt with some mozilla-related customization in the spec file defining how it is built. An example of this is the mercurial package deployed on slaves across the infrastructure.Vanilla packages just need to be made available in our repositories, while mozilla-custom ones need to be rebuilt. The procedure described here applies to mozilla-custom packages. If you're upgrading or modifying an existing mozilla-custom package, you will need the following spec files: * old vanilla spec file: this is the spec file used to build the old version of the package before applying mozilla customizations* new vanilla spec file: this is the spec file used to build the new version of the package before applying mozilla customizations* old mozilla-custom spec file: the spec file used to build the previous mozilla-custom version of the package .spec files can be obtained from source rpm's as described below. === How to extract .spec files from source rpm's === download the source RPM of the old version of the custom package you'd like to build from puppetagain.pub.build.mozilla.org/data/repos/yum/releng/public and unpack it:

You should see a .spec file appear. Check  === What to do with these spec files? === Now that it is you have the old vanilla, new vanilla, and old custom, you should create a new spec file (to be used to build the new version of the package), by merging the diff between old vanilla and old custom (.i.e.: the mozilla customization) into the new vanilla spec file. Spec files used to build packages used in the infrastructure should be identical to the one ones in http://hg.mozilla.org/build/puppet under modules/packages/manifests/mozilla e.g., with an md5 hash. If not, figure out what the differences are, and which corresponds to the running version of the package.