From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MedFs-0006yM-15 for garchives@archives.gentoo.org; Fri, 21 Aug 2009 23:10:44 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 03493E0513; Fri, 21 Aug 2009 23:10:43 +0000 (UTC) Received: from smtp240.poczta.interia.pl (smtp240.poczta.interia.pl [217.74.64.240]) by pigeon.gentoo.org (Postfix) with ESMTP id C3822E0513 for ; Fri, 21 Aug 2009 23:10:42 +0000 (UTC) Received: by smtp240.poczta.interia.pl (INTERIA.PL, from userid 502) id 4AE0942FFBA; Sat, 22 Aug 2009 01:10:42 +0200 (CEST) Received: from poczta.interia.pl (mi03.poczta.interia.pl [10.217.12.3]) by smtp240.poczta.interia.pl (INTERIA.PL) with ESMTP id E551D42FEC0 for ; Sat, 22 Aug 2009 01:10:41 +0200 (CEST) Received: by poczta.interia.pl (INTERIA.PL, from userid 502) id 7EFE03E383C; Sat, 22 Aug 2009 01:10:41 +0200 (CEST) Received: from lebrodyl.localnet (bdl237.neoplus.adsl.tpnet.pl [83.27.253.237]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by www.poczta.fm (INTERIA.PL) with ESMTP id 566213E382B for ; Sat, 22 Aug 2009 01:10:41 +0200 (CEST) From: Maciej Mrozowski To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: RFC: Make 10.0 profiles EAPI-2 'compliant' Date: Sat, 22 Aug 2009 01:10:33 +0200 User-Agent: KMail/1.12.1 (Linux/2.6.30-gentoo-r4; KDE/4.3.0; x86_64; ; ) References: <90b936c0908121058y5fd25cfcm67a19761b1130896@mail.gmail.com> <200908212342.18971.Arfrever@gentoo.org> <20090821224638.1f797d4b@snowmobile> In-Reply-To: <20090821224638.1f797d4b@snowmobile> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2667234.6uMb6f6h99"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200908220110.33794.reavertm@poczta.fm> X-EMID: bad77138 X-Archives-Salt: f29059db-91b3-4de6-87bb-8a8fce795fe1 X-Archives-Hash: 1b3ee9414dcf3bc9434ccb8eab14faf5 --nextPart2667234.6uMb6f6h99 Content-Type: Text/Plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable On Friday 21 of August 2009 23:46:38 Ciaran McCreesh wrote: > On Fri, 21 Aug 2009 23:42:11 +0200 > PMS accurately reflected the Portage documentation at the time it was > written and at the time it was approved. Agreed, but I think it was supposed to reflect Portage 'behaviour' at the=20 time. Of course it's hard to blame anyone for it, especially after all thes= e=20 years. > The correct way to proceed is to use EAPI 4 to move this to be a > specified feature, and to permit it only for profiles marked as using > EAPI 4. It's true, but being able to modularize profile may outweights the need to = be=20 strict-with-the-book here - it's a matter of usefulness. I think it should = be=20 decided by those who actually do the work in profile, whether it's worthy t= o=20 push this now instead of waiting for EAPI approval. So, can profile developers share their view? =2D-=20 regards MM --nextPart2667234.6uMb6f6h99 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEABECAAYFAkqPKWkACgkQFuHa/bHpVdvCbACgpz9MQmdkqrVeSWgPWMxAWSnG vnAAoMIeWKINctFsQpSpgmhYaek2HRrK =9le8 -----END PGP SIGNATURE----- --nextPart2667234.6uMb6f6h99--