[gentoo-dev] cvs keywording.
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. -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] cvs keywording.
-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 ;-) - -- Alin DOBRE Romanian Lead Translator Gentoo Documentation Project: http://www.gentoo.org/doc/en/ Gentoo.RO Community: http://www.gentoo.ro/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDLvesmG51ym6Hu9gRAhPdAKCrID8Dit2/XsitxYl9gWDZy2AqeQCeP0nd FRSrdBcQHAd2p32oMsqeCV0= =569V -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] cvs keywording.
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
Re: [gentoo-dev] cvs keywording.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris Gianelloni wrote: > 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. > Indeed I suck at this :) Sorry games team ;) The other two packages I checked by hand ( and not a craptastic script ) to make sure they were live cvs ebuilds. I have filed bugs [1,2] for them. [1] http://bugs.gentoo.org/show_bug.cgi?id=106663 [2] http://bugs.gentoo.org/show_bug.cgi?id=106662 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQIVAwUBQy/h9GzglR5RwbyYAQIUMQ//Sb/fsEHazPnh9sHTvhCmlyNowfTOhFDO h9kL/mwphuaVtMlXsoXT0DoVNND7Z7+us3UFf6DEDifV0bA5HGtBJj1eNZix+Hyc r9i7D2PHgd9YvUtlaJvW4/C1vRRhobqcKrhzTWKkjhsMkoBlIX5K6dVRDxy/oSv4 /2qc0S8+GQBzpVBvf6JkvK9A5+e/QLbkeTiJAtJwWynbB4j1mPaiam53Uviy/OEw KPnsJhxZb5CVEor2C8hZBRyeczqo4HlYBD8pQDYNMV7NHKItKBatBJVqIAy1FxlQ wYW1i8r2atuxN+xJMSFoSa9fpNLoyQd2Z76Lxlqmy16zatcoKuvp/ONbAnU/lDym ZwbOQVt6Y047Hdkz/RNaxXaBXlq0+2cVLPFZ9VVaMW+d2XCjLrNu3baFRQd6MZyb plRCu6XETJ3hpTzOqvdLTUO1HPUZGBAF2MGtoVmoBuLVaLT96cvb+x75GC29n9xz g8kkILRpZNfE424rqvQb1kaAR3V9z1hQNtCB8Miqe5QQaA7UjDV7UQ6YAjU/ubf2 ZtptEzXHjVAwsZhAeSXen/ImAKUf1G+KvGMpcnVTCRifWNQ8yPYj4+BuXy6BmEWj rZnBUWS/TMADvIHbC3Z8yH0VWSBq5SeXWHtY2lNFVnnGLOI6bcylNhPmFHUu82f8 0onAwV82rDY= =2lVV -END PGP SIGNATURE- -- gentoo-dev@gentoo.org mailing list
