2012/9/1 Křištof Želechovski <yecril71pl@gmail.com>:
Dnia piątek, 31 sierpnia 2012 13:55:06 Dominique Leuenberger a.k.a DimStar pisze:
Also, the patch tagging / annotation has seen a lot of discussion in earlier threads. I know of currently three ways that are actively being used (with their pros and cons): - No tagging at all - 1 - Line tagging in the .spec file, next to the Patch<n>: entry
That should be encouraged by the Web editor before it is imposed as a requirement.
The web editor is a pile of junk and should become un-available; It's not the first time I see people using the web editor to make packages, and this raises one question... Do the vast majority of those people actually test the packages ? :) I've actually found packagers with no openSUSE system installed maintaining packages on OBS...
- Full annotation in the .patch / .diff file.
I do not know how to do it with Kompare but you can make a source file comment instead.
Packaging has nothing to do with KDE specific software; Not everyone uses KDE... in most cases patches should be properly formed through git or svndiff... the sad truth is that no one gives a damn... Comenting the patches on the spec is actually nice and should be how it should work for everyone else; I wonder if professionals do question the rules or if they just follow them (imagine that your software is actually under quality management process that demands absurd things). So all this communism stuff, is really not wanted by many of us. Packaging is about DISCIPLINE, if people can't obbey to it we have chaos, anarchy and turmoil... We have our release team pounded with extra work, we break our workflow and everyone suffers from it.
From my perspective openSUSE should demand superior quality packaging from everyone, specially from the 'professionals' and not support the easy way out. But let me guess... we don't give a damn about quality ;) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org