From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19123 invoked from network); 16 Aug 2004 15:00:52 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 16 Aug 2004 15:00:52 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1Bwiyg-0003HJ-WC for arch-gentoo-releng@lists.gentoo.org; Mon, 16 Aug 2004 15:00:51 +0000 Received: (qmail 28053 invoked by uid 89); 16 Aug 2004 15:00:50 +0000 Mailing-List: contact gentoo-releng-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-releng@lists.gentoo.org X-BeenThere: gentoo-releng@gentoo.org Received: (qmail 4601 invoked from network); 16 Aug 2004 15:00:50 +0000 From: Chris Gianelloni Reply-To: wolf31o2@gentoo.org To: gentoo-releng@lists.gentoo.org In-Reply-To: <20040813185828.GA2481@linux1.home> References: <200408111331.30552.jhuebel@gentoo.org> <200408121836.12316.jhuebel@gentoo.org> <20040813133922.GI1901@time.flatmonk.org> <200408130959.35892.jhuebel@gentoo.org> <20040813185828.GA2481@linux1.home> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-pPjM7/OECwN2SKXU73GN" Organization: Gentoo Linux Message-Id: <1092669014.8655.44.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 16 Aug 2004 11:10:15 -0400 Subject: Re: [gentoo-releng] Re: [gentoo-amd64] Re: 2004.0 Profile Deprecated X-Archives-Salt: 7d45c520-09a3-49a2-b322-2db861096f45 X-Archives-Hash: 3cea5ea5d39d446e60212d44b636ec91 --=-pPjM7/OECwN2SKXU73GN Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2004-08-13 at 14:58, William Hubbs wrote: > I don't see why we need the yearly refreshes either. >=20 > I like the suggestion of making the names more descriptive in stead of us= ing numbers. > Fore example, default/linux/am64. > Then, you might have default/linux/am64/gcc34. > Suppose that you decide to make the default am64 profile use gcc 3.4. Al= l you have to do is merge the am64/gcc34 profile into the am64 profile. > You could do this type of merging with any revision you want to become pa= rt of the default profile, and otherwise not change the default profile at = all. >=20 > What do you think? So how does a user know the profile has changed? What happens to users using the gcc34 profile? What would this do to any of the proposed "stable" portage tree incarnations? I'm all for a profile for each release which *never* changes. Additions can be made as sub-profiles, but a profile never changes. This way things act exactly the same every time. Consistency is a REQUIREMENT for QA. I think creating a profile for each release is very simple. I've created one myself for 2004.2 and I can tell you that it sure was a hard 3 minutes of my life... *grin* Having a stable profile is a definite requirement for any stable project. Since we've been talking with the stable project guys, I think we definitely should not be discussing doing the exact opposite of what is needed to cooperate with them, especially on a separate list which they might not be subscribed to... --=20 Chris Gianelloni Release Engineering QA Manager/Games Developer Gentoo Linux Is your power animal a penguin? --=-pPjM7/OECwN2SKXU73GN 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) iD8DBQBBIM5WkT4lNIS36YERAvdMAJ9BhTWVu9A+PksrTDCXwn4t6BzFLACeIFMk /f4mBIFQrRZk1PKdKo1yt/0= =4top -----END PGP SIGNATURE----- --=-pPjM7/OECwN2SKXU73GN--