From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Iqdzi-0003KP-Oq for garchives@archives.gentoo.org; Sat, 10 Nov 2007 00:14:39 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lAA0DDfd025448; Sat, 10 Nov 2007 00:13:13 GMT Received: from smtp-3.tky.hut.fi (smtp03.tky.fi [82.130.63.73]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lAA0AUmq021732 for ; Sat, 10 Nov 2007 00:10:30 GMT Received: from [82.130.46.196] ([82.130.46.196]) by smtp-3.tky.hut.fi (SMSSMTP 4.1.9.35) with SMTP id M2007111002101510530 for ; Sat, 10 Nov 2007 02:10:15 +0200 Message-ID: <4734F6DE.3030906@gentoo.org> Date: Sat, 10 Nov 2007 02:10:06 +0200 From: =?UTF-8?B?UGV0dGVyaSBSw6R0eQ==?= User-Agent: Thunderbird 2.0.0.6 (X11/20070812) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: RFC: Place of EAPI variable in ebuild References: <4734D767.1080900@gentoo.org> <20071109220423.6db37ff4@blueyonder.co.uk> <4734E263.7050704@gentoo.org> In-Reply-To: X-Enigmail-Version: 0.95.5 OpenPGP: url=http://users.tkk.fi/~praty/public.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3EF06845434B38C4869802F2" X-Archives-Salt: 2ba34ffd-bf17-4100-a943-1aad54fa9b8a X-Archives-Hash: ca717701648da5cddeb8391192dea35c This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3EF06845434B38C4869802F2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Markus Ullmann kirjoitti: >> What if I want to use EAPI=3D1 features in an eclass? So if we for exa= mple >> we have an ebuild using EAPI=3D2 and then it inherits and eclass that = sets >> EAPI=3D1 for slot deps. >=20 > shouldn't be an issue as eapi 1 and 2 would have slot deps > though for other things like src functions defined in the eclass this > might become really interesting, especially if we get src_configure in = eapi2 >=20 > Greetz > Jokey >=20 You didn't get my point. Unless inherit has some EAPI handling logic setting EAPI in an eclass would overwrite the one in the ebuild. Regards, Petteri --------------enig3EF06845434B38C4869802F2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHNPbhcxLzpIGCsLQRApYaAJwJnzr5XUgmPoxAlPFPeBqGfkHFqwCgmVtL zELmroo+9dI2KonNLIZNugc= =qhOG -----END PGP SIGNATURE----- --------------enig3EF06845434B38C4869802F2-- -- gentoo-dev@gentoo.org mailing list