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 1Mex57-0008Sr-A7 for garchives@archives.gentoo.org; Sat, 22 Aug 2009 20:20:57 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 83EA2E02EF; Sat, 22 Aug 2009 20:20:55 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 655AAE02EF for ; Sat, 22 Aug 2009 20:20:55 +0000 (UTC) Received: from afta-gentoo.localnet (ip-85-198-235-97.broker.com.pl [85.198.235.97]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id D5B0166875 for ; Sat, 22 Aug 2009 20:21:00 +0000 (UTC) From: Arfrever Frehtes Taifersar Arahesis To: Gentoo Development Subject: Re: [gentoo-dev] Re: RFC: Make 10.0 profiles EAPI-2 'compliant' Date: Sat, 22 Aug 2009 22:22:54 +0200 User-Agent: KMail/1.12.0 (Linux/2.6.30-tuxonice-r5-AFTA; KDE/4.3.0; x86_64; ; ) References: <90b936c0908121058y5fd25cfcm67a19761b1130896@mail.gmail.com> <4A8F41BE.4090509@allenjb.me.uk> <20090822203947.7bee89ef@snowcone> In-Reply-To: <20090822203947.7bee89ef@snowcone> 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="nextPart2603385.mIWvnCZYAE"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200908222222.59190.Arfrever@gentoo.org> X-Archives-Salt: afa341e3-4386-4cce-97f1-d1afe8b7d348 X-Archives-Hash: d02065acc4af5aa6b6b7ffbe93d0c65f --nextPart2603385.mIWvnCZYAE Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 2009-08-22 21:39:47 Ciaran McCreesh napisa=C5=82(a): > On Sat, 22 Aug 2009 01:54:22 +0100 > AllenJB wrote: > > Could there be room for "fast track" EAPI's to be considered on some > > occasions - eg. in this case an EAPI-2.1 which is simply EAPI-2 with > > the "package.* as directory in profiles" feature included? >=20 > It's a possibility, since it's zero cost for Portage and an easy one > to word into the specification. >=20 > Another possibly nicer option would be to add the feature into EAPI 3. > However, if we're considering this, we'd have to be absolutely totally > clear that this isn't a call to open up EAPI 3 for yet more changes. EAPI=3D3 can be opened also for other changes trivial to implement (e.g. al= lowing bash-4.0 features). =2D-=20 Arfrever Frehtes Taifersar Arahesis --nextPart2603385.mIWvnCZYAE Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) iEYEABECAAYFAkqQU6MACgkQIEGVSeBq/j5DRgCfevmpjq076tSpRmT0IMw5NvhP MdAAnAyqEXTLkGjYVcyX1IU2lLlRdGEX =SRhg -----END PGP SIGNATURE----- --nextPart2603385.mIWvnCZYAE--