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 1IrI6i-0002kp-3n for garchives@archives.gentoo.org; Sun, 11 Nov 2007 19:04:32 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lABJ3cox025466; Sun, 11 Nov 2007 19:03:38 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 lABJ1lwr023154 for ; Sun, 11 Nov 2007 19:01:47 GMT Received: from [82.130.46.215] ([82.130.46.215]) by smtp-3.tky.hut.fi (SMSSMTP 4.1.9.35) with SMTP id M2007111121014609075 for ; Sun, 11 Nov 2007 21:01:46 +0200 Message-ID: <47375195.9060400@gentoo.org> Date: Sun, 11 Nov 2007 21:01:41 +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> <20071109220724.GK19739@gentoo.org> In-Reply-To: <20071109220724.GK19739@gentoo.org> 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="------------enigFC8F8F4E673D50C35E08AF93" X-Archives-Salt: 456c184a-41cf-444c-b973-980f2ea1c0dd X-Archives-Hash: b96c2b1bac52e26f1602505d181b0175 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFC8F8F4E673D50C35E08AF93 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Fabian Groffen kirjoitti: > On 09-11-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 w= e >> put it it after LICENSE as that's where the more technical stuff like >> SLOT starts. Attached a patch for skel.ebuild. >=20 > Just my 2 cents, I have placed EAPI right after the # $Header: line of > each ebuild, as I felt that it was the first thing to know of the > ebuild, as it describes how you possibly have to process the rest of th= e > ebuild. Examples can be found in the prefix overlay, e.g. > http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/app-sh= ells/bash/bash-3.2_p17-r00.1.ebuild >=20 > It has the advantage for me that EAPI is never hidden away somewhere > down the ebuild, and it is just inserted by a simple bash script > automagically (eapify in this case). >=20 If we go with this solution then I guess eclasses must check for the EAPI variable and then act accordingly. For example if the ebuild sets EAPI=3D2 and the eclass is designed for EAPI=3D1 then it could be made to= die in case EAPI 2 is not backwards compatible. The main reason for me asking this it that I plan to make the java eclasses use the EAPI 1 features. Regards, Petteri --------------enigFC8F8F4E673D50C35E08AF93 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 iD8DBQFHN1GYcxLzpIGCsLQRAlUKAJ4mRUca1hNMHD0DIfq3BM3VeAuw3ACdHDdc Z+WT4BdiUnwaVOL1HFyRrdM= =dz2P -----END PGP SIGNATURE----- --------------enigFC8F8F4E673D50C35E08AF93-- -- gentoo-dev@gentoo.org mailing list