On Friday 16 September 2005 21:34, Ciaran McCreesh wrote: > On Fri, 16 Sep 2005 15:15:26 -0400 Mike Frysinger <[EMAIL PROTECTED]> > > wrote: > | not really ... sometimes you want to keep a package in unstable > | forever (like the cvs snapshots i make of e17), or until you work > | some quirks/features out for a new revbump which you would want stable > > 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. Paul -- Paul de Vrieze Gentoo Developer Mail: [EMAIL PROTECTED] Homepage: http://www.devrieze.net
pgpoS8zYyetNS.pgp
Description: PGP signature
