Re: [gentoo-dev] first council meeting

[Olivier Crete <tester@gentoo.org>]

On Fri, 2005-16-09 at 16:21 -0400, Aron Griffis wrote:
> Paul de Vrieze wrote:[Fri Sep 16 2005, 04:11:14PM EDT]
> > > Those should be in package.mask. ~arch is for candidates for arch that
> > > haven't yet proven themselves.
> > 
> > It's often the case that those ebuilds in principle work, but there
> > are other reasons for not marking stable yet. Some packages for
> > example can have upgrade problems for stable users while being
> > stable for testing (by benefit of allready having passed such
> > upgrade problems). Masking the ebuild is not really an option
> > (causing testing users to go through unnecessary hoops again), while
> > marking stable is also no option.
> 
> You're saying there's four states:
> 
>     package.mask
>     ~arch
>     ~arch candidate for arch
>     arch
[...]
> So far I find myself agreeing with Ciaran's idea in this thread.
> I don't see the point (yet) in more than three states.

Well having the "~arch candidate for arch" makes the imlate script much
easier to use.. I would find it a PITA to have to go through the
changelog of every package to see if it has been in testing for 30
days.. Or we need to automate it, something like a
imlate-because-the-package-hasnt-changed-in-30-days.py 

-- 
Olivier Crête
tester@gentoo.org
Gentoo Developer
x86 Security Liaison


-- 
gentoo-dev@gentoo.org mailing list