Re: [gentoo-dev] proposed solution to arches/stable problem

[Travis Tilley]

On Tuesday 22 June 2004 10:44 am, Aron Griffis wrote:
>     1. Repoman could check keyword changes, warning arch maintainers
>        when they mark a version arch-stable that is not marked stable
>        by the maintainer.

actually, i'd love to have something that's repoman-activated. that would also 
be a great slap on the wrist reminder any time i'm tempted to do otherwise 
without first talking to the herd maintainers. ^^;

i'd prefer a different variation.. perhaps a "known issues exist" or "beware 
of dragons" flag of some sort. but any useful variation of this theme that's 
repoman activated would be nice. *shrug* foser's idea of having an ebuild 
mention the maintainer's arch(s) would probably also work if repoman knows 
about it... but there are a lot of semi-but-not-really maintained ebuilds.

but then again... i'd always have to mark gcc 3.4 as "known issues exist" even 
though it's stable on my arch and needed to fix other bugs. there are a few 
issues with unit-at-a-time still that cause internal compiler errors on a few 
archs among other things. hmm. in this case, it makes sense to completely 
ignore a "beware" flag on some archs (amd64, ppc64, mips)... but gcc tends to 
be a special case anyways.

i also think that there will always be strange special cases, but having 
repoman constantly remind you would go a long way in keeping the number of 
special cases down... and a reminder to communicate with the maintainer(s), 
like in the hppa mldonkey example (where communication seemed to be the only 
thing lacking, not proper QA). as much as i dislike repoman's bugs, it would 
be useful indeed.

just to clarify: i dont think this is something to prevent archs from 
determining special cases as needed, just something to force some extra 
thinking and remind arch maintainers that there are probably extra steps 
involved that should be taken first.


-- 

Travis Tilley <lv@g.o>

--
gentoo-dev@g.o mailing list