From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11075 invoked from network); 20 Aug 2004 15:40:26 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 20 Aug 2004 15:40:26 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1ByBVA-0001C3-QH for arch-gentoo-releng@lists.gentoo.org; Fri, 20 Aug 2004 15:40:25 +0000 Received: (qmail 14409 invoked by uid 89); 20 Aug 2004 15:40:24 +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 26341 invoked from network); 20 Aug 2004 15:40:24 +0000 From: Jason Huebel Organization: Gentoo To: gentoo-releng@lists.gentoo.org Date: Fri, 20 Aug 2004 10:40:59 -0500 User-Agent: KMail/1.7 References: <200408111331.30552.jhuebel@gentoo.org> <200408121836.12316.jhuebel@gentoo.org> <1093014598.31457.16.camel@woot.uberdavis.com> In-Reply-To: <1093014598.31457.16.camel@woot.uberdavis.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2346362.3l7PvrI2bS"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200408201041.07855.jhuebel@gentoo.org> Subject: Re: [gentoo-releng] Re: [gentoo-amd64] Re: 2004.0 Profile Deprecated X-Archives-Salt: 70a66f48-5f99-4cff-b4e8-ac7a7e0307a6 X-Archives-Hash: 464c2b827fd19fa4e9253e95a85534fe --nextPart2346362.3l7PvrI2bS Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 20 August 2004 10:09 am, John Davis wrote: > OK - > I am going to try and make sense of all of the good discussion here by > putting it into a draft proposal. From what I have gleaned off of the > thread, this is the implementation that we are looking for regarding > general profile policy: > > Profiles will adhere to the following layout standard: > default-linux/$arch/20xx > default-linux/$arch/20xx-r1 > default-linux/$arch/20xx-r2 > (and so forth) > > Each year, a new profile has to be created (20xx). Each subsequent major > revision to the 20xx profile will be marked as -rx, where x is the > revision number. > > The top level arch directory (default-linux/$arch) will contain a > ChangeLog that will serve as a record log for each profile revision and > change. > > How does that sound? Am I missing anything? Looks good to me. Quick (slightly OT) question: Is there any limit on the= =20 directory depth of a cascading profile? =2D-=20 Jason Huebel Gentoo/amd64 Strategic Lead Gentoo Developer Relations/Recruiter GPG Public Key: http://pgp.mit.edu:11371/pks/lookup?op=3Dget&search=3D0x9BA9E230 "Do not weep; do not wax indignant. Understand." Baruch Spinoza (1632 - 1677) --nextPart2346362.3l7PvrI2bS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBBJhuTbNgbbJup4jARAl5bAJ92U5gYVXRvF24CrDcy6I6CGNchfwCgiJlU VmgNy0hDY9f5OpWGLfRYfwg= =yuhV -----END PGP SIGNATURE----- --nextPart2346362.3l7PvrI2bS--