From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9539 invoked from network); 20 Aug 2004 15:10:09 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 20 Aug 2004 15:10:09 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1ByB1t-0003Cr-3R for arch-gentoo-releng@lists.gentoo.org; Fri, 20 Aug 2004 15:10:09 +0000 Received: (qmail 13307 invoked by uid 89); 20 Aug 2004 15:10:07 +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 20205 invoked from network); 20 Aug 2004 15:10:06 +0000 From: John Davis Reply-To: john_davis@pauldavisautomation.com To: gentoo-releng@lists.gentoo.org In-Reply-To: <200408121836.12316.jhuebel@gentoo.org> References: <200408111331.30552.jhuebel@gentoo.org> <200408121705.16986.jhuebel@gentoo.org> <1092352858.20370.5.camel@woot.uberdavis.com> <200408121836.12316.jhuebel@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-SvevIOW6szwst/XsQr8J" Organization: Paul Davis Automation, Inc. Message-Id: <1093014598.31457.16.camel@woot.uberdavis.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 20 Aug 2004 11:09:58 -0400 X-Virus-Scanned: by amavisd-new at mail.pauldavisautomation.com Subject: Re: [gentoo-releng] Re: [gentoo-amd64] Re: 2004.0 Profile Deprecated X-Archives-Salt: 368e93ef-ecab-4025-a449-8040a3db6421 X-Archives-Hash: 7396cfca1adfa9e4ecb037a800e98384 --=-SvevIOW6szwst/XsQr8J Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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? Cheers, --=20 John Davis Gentoo Linux Developer ---- GnuPG Public Key: Fingerprint: 4F9E 41F6 D072 5C1A 636C 2D46 B92C 4823 E281 41BB --=-SvevIOW6szwst/XsQr8J 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) iD8DBQBBJhRGuSxII+KBQbsRAkEmAKDPc9tRKfx7YTdlg7oiHfmKikoRqwCgy4KV WkqqnLDvc5CU4749qn01LL0= =eePL -----END PGP SIGNATURE----- --=-SvevIOW6szwst/XsQr8J--