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 1Iqcc3-0006hW-SV for garchives@archives.gentoo.org; Fri, 09 Nov 2007 22:46:08 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lA9MjEDL032736; Fri, 9 Nov 2007 22:45:14 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 lA9MgnlC029450 for ; Fri, 9 Nov 2007 22:42:49 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 M2007111000424807664 for ; Sat, 10 Nov 2007 00:42:48 +0200 Message-ID: <4734E263.7050704@gentoo.org> Date: Sat, 10 Nov 2007 00:42:43 +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] RFC: Place of EAPI variable in ebuild References: <4734D767.1080900@gentoo.org> <20071109220423.6db37ff4@blueyonder.co.uk> In-Reply-To: <20071109220423.6db37ff4@blueyonder.co.uk> 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="------------enigE0460653E3F3803B603E6C03" X-Archives-Salt: 57d0f90a-22ee-4b48-973a-d2ba5214f716 X-Archives-Hash: 75812aefd4674c8b99a16a0ab14bb93a This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE0460653E3F3803B603E6C03 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ciaran McCreesh kirjoitti: > On Fri, 09 Nov 2007 23:55:51 +0200 > Petteri R=C3=A4ty wrote: >> Usually it's best that ebuild variables follow the order that is in >> skel.ebuild. So know we should decide where to place EAPI. I suggest >> we put it it after LICENSE as that's where the more technical stuff >> like SLOT starts. Attached a patch for skel.ebuild. >=20 > It needs to go right at the top, before 'inherit'. >=20 What if I want to use EAPI=3D1 features in an eclass? So if we for exampl= e we have an ebuild using EAPI=3D2 and then it inherits and eclass that set= s EAPI=3D1 for slot deps. Regards, Petteri --------------enigE0460653E3F3803B603E6C03 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 iD8DBQFHNOJjcxLzpIGCsLQRAjt1AKCOCnFEXS9XBZ2ZD+giObmCp6861gCgmZGn qUP/XVPzEnGRqmssIqJV3Gs= =ODgs -----END PGP SIGNATURE----- --------------enigE0460653E3F3803B603E6C03-- -- gentoo-dev@gentoo.org mailing list