----- Original Message -----
From: "Bill Nottingham" <notting(a)redhat.com>
To: "Development discussions related to Fedora"
<devel(a)lists.fedoraproject.org>
Sent: Tuesday, August 21, 2012 5:59:29 PM
Subject: Re: Mass changes to packaging
Jason L Tibbitts III (tibbs(a)math.uh.edu) said:
>>>>> "RWMJ" == Richard W M Jones
<rjones(a)redhat.com> writes:
RWMJ> I just received about a dozen bugs like this:
Yep, someone has taken it upon themselves to mass-file a bunch of
unnecessary tickets.
When FPC makes guidelines changes, they aren't generally accompanied by
some mandate that existing packages be changed. In fact, I can't think
of a time when a change was made retroactive. If there was something
that had to change in a bunch of packages, we'd at least try to organize
a labor pool to get that done without having to endlessly bug every
package maintainer.
This stems from a request of mine, and is therefore my fault..
Presets are a valuable new feature for both distribution constructors
and administrators - rather than having a single hardcoded policy *in
the packages* about what starts and doesn't start (and requires rebuilding
to fix), presets allow an easy way for:
- administrators
- provisioners
- spin maintainers
to easily define what should & shouldn't be running for their install.
However, it will take some work to get that done across the repository of
packages, so I requested that Vaclav, Lukas, Michal, and any others look
into what is needed to do this work in the repository. I had intended for
them to provide patches and an offer to commit, but I didn't communicate
that clearly to them. Apologies to those worried by these requests, and
to Vaclav, Lukas, and Michal for anything that comes their way.
Bill
--
devel mailing list
devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Sorry for this mess. After a discussion, we have decided, that the best way would be to
create bugs for every packages and then helping creating patches for specfiles. We want to
give maintainers possibility to fix this on their own and because we want this change in
all packages, creating bug seemed as a better option then spamming devel-list.
Lukas