El 29/08/12 13:52, Dimstar / Dominique Leuenberger escribió:
On Wed, 2012-08-29 at 19:41 +0200, Guido Berhoerster wrote:
Making patch tags mandatory would be again very useful since they are easily machine-parseable and could be read and displayed in OBS in order to get a quick overview on the purpose and status of all patches of a particular package. Right now I'm using my own script to generate a HTML patch report for all of my packages. There are way too many packages which have obscure foo.dif patches without any explanation whatsoever neither inline, in the spec or changelog. This makes packages practically only maintainable by the person who created them.
Or someone that can actually read code ? doh !
I do agree as well on the PATCH- Tag line (the 'forces patchers to report them upstream' is a very good reason), but also know that there is a lot of resistance against this one (there were a lot of discussions around them).
There is resistance, because it is non-sense, for that we already have: - Version control systems - Inline patch headers - Bugzilla or other trackers Sending patches to upstream is a fine idea in theory, but unless you have the time and patience to register in a dozen of trackers, mailing lists and to provide a patch that will work on at least Linux, Windows, BSD, MAC OS, different kernel or library versions this only results in a burden that I personally do not want or care. I want openSUSE be better and working, that 's all I care about. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org