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 1IriVu-0001Eg-4Y for garchives@archives.gentoo.org; Mon, 12 Nov 2007 23:16:18 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.2/8.14.0) with SMTP id lACNEAJ0022049; Mon, 12 Nov 2007 23:14:10 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 lACNC1Rr019427 for ; Mon, 12 Nov 2007 23:12:01 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 M2007111301120013474 for ; Tue, 13 Nov 2007 01:12:00 +0200 Message-ID: <4738DDB8.2080801@gentoo.org> Date: Tue, 13 Nov 2007 01:11:52 +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> In-Reply-To: <4734D767.1080900@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="------------enigBC899A9E1E5BBB194476DC78" X-Archives-Salt: 4178c289-e590-4fee-974c-c5769c30f76e X-Archives-Hash: 2e121a7e73304ccde70fbca12bf143ce This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBC899A9E1E5BBB194476DC78 Content-Type: multipart/mixed; boundary="------------020706050301020608050506" This is a multi-part message in MIME format. --------------020706050301020608050506 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Petteri R=C3=A4ty kirjoitti: > 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 > Regards, > Petteri >=20 The predominant options seems to be before inherit so let's go with that then. Will post more details on eclass stuff once I get further with java stuff. 00:31 < Betelgeuse> zmedico: ping 01:02 < zmedico> Betelgeuse: pong 01:03 < Betelgeuse> zmedico: Haven't seen your thoughts on EAPI place in ebuild 01:05 < zmedico> I'd say the ebuild should define it before the inherit 01:05 < zmedico> that's the simplest and safest thing to do 01:05 < Betelgeuse> zmedico: ok so I would test for EAPI=3D1 then in java= eclasses? 01:05 < Betelgeuse> zmedico: And maybe write eapi.eclass for testing EAPI version 01:06 < Betelgeuse> zmedico: eapi 1 && etc 01:06 < Betelgeuse> If I only need one function then perhaps add it to eutils 01:06 < zmedico> sure 01:06 < zmedico> yeah Regards, Petteri --------------020706050301020608050506 Content-Type: text/plain; name="eapi-location.patch" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="eapi-location.patch" SW5kZXg6IHNrZWwuZWJ1aWxkCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC92YXIvY3Zzcm9v dC9nZW50b28teDg2L3NrZWwuZWJ1aWxkLHYKcmV0cmlldmluZyByZXZpc2lvbiAxLjQyCmRp ZmYgLXUgLXIxLjQyIHNrZWwuZWJ1aWxkCi0tLSBza2VsLmVidWlsZAkxIEphbiAyMDA3IDEy OjE4OjE3IC0wMDAwCTEuNDIKKysrIHNrZWwuZWJ1aWxkCTEyIE5vdiAyMDA3IDIzOjA5OjM1 IC0wMDAwCkBAIC0xMSw2ICsxMSwxMSBAQAogIyB3aWxsIGJlIGNvbW1pdHRlZCB0byBjdnMs IHRoZSBkZXRhaWxzIG9uIHRoYXQgbGluZSB3aWxsIGJlIGF1dG9tYXRpY2FsbHkKICMgZ2Vu ZXJhdGVkIHRvIGNvbnRhaW4gdGhlIGNvcnJlY3QgZGF0YS4KIAorIyBUaGUgRUFQSSB2YXJp YWJsZSB0ZWxscyB0aGUgZWJ1aWxkIGZvcm1hdCBpbiB1c2UuCisjIERlZmF1bHRzIHRvIDAg aWYgbm90IHNwZWNpZmllZC4gU2VlIGN1cnJlbnQgUE1TIGRyYWZ0IGZvciBtb3JlIGRldGFp bHMuCisjIEVjbGFzc2VzIHdpbGwgdGVzdCBmb3IgdGhpcyB2YXJpYWJsZSBpZiB0aGV5IG5l ZWQgdG8gdXNlIEVBUEkgPiAwIGZlYXR1cmVzLgorRUFQST0xCisKICMgaW5oZXJpdCBsaXN0 cyBlY2xhc3NlcyB0byBpbmhlcml0IGZ1bmN0aW9ucyBmcm9tLiBBbG1vc3QgYWxsIGVidWls ZHMgc2hvdWxkCiAjIGluaGVyaXQgZXV0aWxzLCBhcyBhIGxhcmdlIGFtb3VudCBvZiBpbXBv cnRhbnQgZnVuY3Rpb25hbGl0eSBoYXMgYmVlbgogIyBtb3ZlZCB0aGVyZS4gRm9yIGV4YW1w bGUsIHRoZSAkKGdldF9saWJkaXIpIG1lbnRpb25lZCBiZWxvdyB3b250IHdvcmsK --------------020706050301020608050506-- --------------enigBC899A9E1E5BBB194476DC78 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 iD8DBQFHON27cxLzpIGCsLQRAnE0AKCOvE1JgC/1aMksZk4oBUTu1HfhsgCfT/J1 RMJKXj4gegpGtMgrmWXKEQ0= =f2T+ -----END PGP SIGNATURE----- --------------enigBC899A9E1E5BBB194476DC78-- -- gentoo-dev@gentoo.org mailing list