This page should, over time, evolve into a set of rules and policies that we can all follow in the CentOS Ecosystem. At the moment, its just a set of guidelines.
Build System Specifics
- In order to test what version of CentOS the package is being built for you can use the 'centos_ver' macro.
Patches
- When patching upstream code its important to be able to identify easily and clearly what patches are introduced by CentOS. Therefore:
- Name should start with 'centos' ( all lowercase ). eg: centos-xxxxx.patch
- If the patch is specific to a package, include the name : eg: centos-anaconda-xxxx.patch would be good for an anaconda specific patch.
- Include, very briefly, what is being attempted in the patch. eg: centos-anaconda-remove-upstream-branding.patch would be a good name for a patch that aims to remove upstream branding in anaconda for CentOS.
Include enough info in the changelog so as to make it easy for package metadata management process's and yum to be able to produce relevant info. eg: "Added centos-yumutils-enable-extra-plugins (#<YY>)"
- Try to include an issue number from bugs.centos.org and include those in parenthesis at the end of a changelog line
- Try and restrict patches to single functions, as much as possible. Its fine to have multiple patches.
