[gentoo-dev] Re: RFC: reduce conflicts, separate keywording from ebuilds

[Stefan Schweizer]

George Shapovalov schrieb:
> a) move all the keywording into profiles (that is remove all KEYWORDS fields
> from all the ebuild) and disallow package maintainers and other devs (other
> than arch teams) to touch keywords
>
> or
>
> b) leave ebuilds with simple ~arch/arch/-arch (literally) keywords and move
> granular per-arch settings to profiles

the first one + maintainer arch is what I like to have. Other arches can 
then go up to maintainer arch automatically(with a bot) for ~arch and 
manually for arch or define their own policies like they want.

> or something else? Even then I am not sure how either of these is going to
> work, especially this:
>> The arch team can then decide themselves which ebuild they want to mark
>> ~arch and they can take care of possible new dependencies themselves.
>
> normally new versions/packages go directly into ~arch unless they are
> transiently masked by developer (waiting for release, etc) or are permanently
> masked live-cvs/svn ones.
The particular case is about having new depends in new versions. For 
example in ghostscript-esp-8.15.3-r1 there is a new dependency on 
app-text/djvu and mips, arm, s390 and sh do not keyword it. See bug 
148945 too.

moving keywording only in the arch teams responsibility is the way to go 
imo because I hate having keywording bugs assigned to my herd where I 
can do nothing about it.

> I am not sure how a) is going to work at all in
> this respect. Are we going to get tons of ebuilds just sitting there never
> made visible to any arch now (since even x86 would have a large backlog)?

it can be automated to do this from the maintainer arch if the arch team 
wants it.

-Stefan

-- 
gentoo-dev@g.o mailing list