On Mon, 2005-09-19 at 20:38 +0300, Alin Dobre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Alec Warner wrote: > > Official policy states that CVS ebuilds should never be marked > > stable[1]. Yet many ebuilds that are based on cvs sources and are > > marked stable on arch's. I would like to know why this is so. > > > > ./net-misc/netcomics-cvs/netcomics-cvs-0.14.1.ebuild:KEYWORDS="x86 ~amd64" > > ./games-fps/blackshades-cvs/blackshades-cvs-20031110.ebuild:KEYWORDS="x86 > > ~ppc ~amd64" > > ./dev-embedded/sdcc-cvs/sdcc-cvs-2.4.0-r1.ebuild:KEYWORDS="x86 ~ppc amd64" > > ./games-fps/avp-cvs/avp-cvs-20031110.ebuild:KEYWORDS="x86" > > > > This was just a hacked up search I did on the tree while in class, and > > is no way inclusive of all packages breaking policy. If you want bugs > > for them, I 'll make them. > > [1] > http://devrel.gentoo.org/handbook/handbook.xml?part=2&chap=3#doc_chap1_sect9 > > ;-)
The two games listed are CVS snapshots, not live CVS builds. A live CVS build should never be stable. A snapshot is a known set of files, and can be marked stable. It is usually a known-good working set of files, taken from CVS, but not tied to an actual "release" version, and added to our mirrors by the package maintainers. -- Chris Gianelloni Release Engineering - Strategic Lead Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
