On Friday 16 September 2005 21:34, Ciaran McCreesh wrote:
> Those should be in package.mask. ~arch is for candidates for arch that
> haven't yet proven themselves.

No. Your idea how it should work simply doesn't match reality. When you e.g. 
have upstream devs following the maxim "release early and often", it happens 
that you don't want ebuilds go stable so easily, but still have a wide 
testing audience. Arch teams have to ask package maintainers when they want 
to stabilize an ebuild before it is indicated - be it by a "maint" keyword or 
what else.


Carsten