[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Review queue/FESCo after the merge

On 19.11.2007 10:55, Patrice Dumas wrote:
> On Mon, Nov 19, 2007 at 06:56:22AM +0100, Thorsten Leemhuis wrote:
>> Someone in a lot cases (like this one) could just realize many of the
>> changes in the Packaging Guidelines directly in CVS for all effected
>> packages. I think we should do that way more often and get away from the
>> mantra "this is my package and nobody else is allowed to touch it" --
>> that's why I took this particular issue as example to just show how it
>> could be done. Now I expect from FESCo advice for this particular
>> example as well as the general concept where one persons realizes
>> changes in all effected packages directly in CVS.
> I fully agree, but it is already explicitely permitted in
> http://fedoraproject.org/wiki/PackageMaintainers/Policy/WhoIsAllowedToModifyWhichPackages

Well, I actually wrote most of it, but reality and documentation are two
different things afaics, thus...

> All is needed is a set of scripts and maybe FESCo taking a lead. 

...FESCo really is the one that needs to take a lead and say "we want
that". Especially because some of the packages might be protected by
ACLs, which creates further problems.

> One
> occasion I see would be the mass rebuild of packages that depend on
> doxygen after the 'non reproducible anchors bug' is fixed -- that is
> doxygen is updated to latest version.

Firefox IMHO is the way better example -- I fail to understand why we
didn't create a script that rebuilds all packages that depend on it once
it's build and in the buildroot. Yes,

 * that could delay the firefox push by one hour or a bit more -- small
problem, but not a big one, as stuff often gets delayed by other things
as well (the ones with access to the keys being asleep for example)

 * some packages might not compile with the new firefox (but most likely

but that's way better then a broken repo, as a new firefox in the repo
is not much of a help if it won't get installed on the systems by yum,
as most will have yelp or other stuff installed that needs the exact
version of firefox it was build against.

Actually creating such a script was the plan early this year when I
still was FESCo chair, but seems the person that wanted to take care of
it forgot about it in the merge noise (no wonder with all those changes,
so I don't blame him).


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]