On Wed, 29 Aug 2012 17:52, Cristian Rodríguez
On 29/08/12 08:42, Dominique Leuenberger a.k.a DimStar wrote:
Dear Factory contributors and packagers,
As openSUSE 12.2 is frozen and Factory is 'open to go wild' again, I would like to announce that the packaging guidelines have some extensions (not really new) that will be stricter enforced than they used to be.
Currently a common rule to be 'ignored' or packagers are not aware is around the topics of: - .Changes entries - Patches
Sad to hear this non-sensical, redundant rules are trying to be enforced without any discussion.
This is what I call "packaging bureaucracy", Source code changes are mentioned in the NEWS, Changelog, URL, etc of the package and patches are mentioned in the spec file, with their addition time available in the OBS history.
Increasingly frustrated, Cristian.
Think of the following: A package does an upstream update (say to 2.4.5). Now the package.chances gets some new lines: ===== 2012-08-28 update to version 2.4.5 * this obsoletes OSS patch1 and patch3 * this obsoletes SLE patch4 * generic (non-distro) patches [2,5,7] are obsolete * gcc 4.5 and clang 3.1 are now fully supported. * NEW patch8 b/c of off-by-one error in main.c ===== Ask yourself: is this info in: * NEWS (from upstream) - NO * Changelog (also upstream) - NO * package.spec - Not reliable and not visible from outside And best of all you can get this info via rpm on a compiled package. Those comments in the spec-file? NO chance. Yes, care and nurturing of the .changes file is work. But it is not for naught. I'm not trying to open the door by running headfirst in it. I agree that info that is in NEWS and Changelog should at most be referenced, not repeated. -- Yamaban.