Mailinglist Archive: opensuse-packaging (158 mails)

< Previous Next >
Re: [opensuse-packaging] Package Markup / Package Tagging
  • From: "Dominique Leuenberger" <Dominique.Leuenberger@xxxxxxxxxxxxx>
  • Date: Mon, 06 Sep 2010 10:18:08 +0200
  • Message-id: <4C84BFE0020000290009A9BA@xxxxxxxxxxxxxxxxxxx>
On 09/06/2010 at 10:06 AM, Michal Marek <mmarek@xxxxxxx> wrote:
So let's rather put the burden on the packagers? Because editing a two
(three, four ... or how much metadata are you going to stuff there)
times longer spec file is so much more fun? Requiring people to do more
(boring) work just because it is then easier to gather some fancy stats
is totally crazy. I really hope this won't become an official policy.
And even if it will, I'm not going to follow it, I'm sure you will save
so much time by not improving the script that you can maintain these
annotations yourselves :-P.

Burden? Writing a one phrase sentence with references what the next line is
There are spec files I'm certainly never going to touch. Having a gazillion of
patches in any package is not the right thing to do anyway... this
simply does not scale and is a pain when an update

The tag line is not only for scripts, that's for sure.. but also for other
people hacking on your spec files (everybody should be able to touch every
package, no?)

Especially when doing an upgrade of a package with 20 patches, it can be so
very helpful to know immediately which patches make sense. An update of a
package typically makes me open two files: the .changes to document what I do
and the .spec to fix the build and remove unneeded stuff and add new
deps as needed.

A patch that still applies to not mean it's still needed! Having the
bnc/kde/bgo whatever bug id can help spot that a patch is no longer required.
Yes, packaging IS taking time, it's not to be handled in 4 minutes during lunch

To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups