From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14419 invoked from network); 10 Aug 2004 13:20:41 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 10 Aug 2004 13:20:41 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BuWYT-0008OX-Dt for arch-gentoo-dev@lists.gentoo.org; Tue, 10 Aug 2004 13:20:41 +0000 Received: (qmail 2177 invoked by uid 89); 10 Aug 2004 13:20:40 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 29985 invoked from network); 10 Aug 2004 13:20:40 +0000 From: Chris Gianelloni Reply-To: wolf31o2@gentoo.org To: gentoo-dev@lists.gentoo.org In-Reply-To: <1092099889.21951.26.camel@montreal> References: <20040808185144.GB29077@mail.lieber.org> <1092061268.30233.18.camel@localhost> <20040810000107.GX29077@mail.lieber.org> <200408091913.36607.cshields@gentoo.org> <1092099889.21951.26.camel@montreal> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-84gpVSEUyFykVzAgApaG" Organization: Gentoo Linux Message-Id: <1092144447.21445.23.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 10 Aug 2004 09:27:27 -0400 Subject: Re: [gentoo-dev] GLEP 19, reloaded (again) X-Archives-Salt: 5c10f899-3fd8-415e-bc14-1616ff55db4e X-Archives-Hash: 36ac421a89a5caf17b677f9550942137 --=-84gpVSEUyFykVzAgApaG Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2004-08-09 at 21:04, Olivier Crete wrote: > Having a stable system double or tripes the amount of work every time > anyways because we need to test on each "stable tree".. Newer versions > might not work anyways.. CVS work is very little compared to testing > work. Exactly. This is why I think separate trees is the way to go. If you're already having to test for *every* ebuild, why make it more complex by having TONS of "stable" ebuilds in the same tree. With a separate tree, one can simply test against the packages IN THAT TREE AND NO OTHER and get an accurate test of what the user would see. > > One quick hack is to just sync the full tree to the stable tree without= the=20 > > --delete option, so that everything old stays and we get all of the new= =20 > > programs. Any updates we want to activate would need to be modified in= the=20 > > profiled mask files. No CVS work for the tree involved here. >=20 > The problem with that is that the tree for stable users will start > growing and they will start getting lots of old crap... And it doesnt > give us separation of "base" and "updates" that I think many "corporate" > types want..=20 arch is base... ~arch is updates... This is simple. For people that want all the updates, they set ACCEPT_KEYWORDS to ~arch. For people that want to verify updates, they simply re-KEYWORD the package once they've approved it. --=20 Chris Gianelloni Release Engineering QA Manager/Games Developer Gentoo Linux Is your power animal a penguin? --=-84gpVSEUyFykVzAgApaG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBGM0/kT4lNIS36YERAukZAJ4hjJjHd77uEZI1DTY81TXLSs1tIQCeN4Jj 1qQYVVN2YeJbhGxWg6XWsKg= =JAaX -----END PGP SIGNATURE----- --=-84gpVSEUyFykVzAgApaG--