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 1IrIPp-000452-Lk for garchives@archives.gentoo.org; Sun, 11 Nov 2007 19:24: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 lABJNRW8003721; Sun, 11 Nov 2007 19:23:27 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 lABJLZ0o001388 for ; Sun, 11 Nov 2007 19:21:35 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 M2007111121213511151 for ; Sun, 11 Nov 2007 21:21:35 +0200 Message-ID: <4737563A.9020303@gentoo.org> Date: Sun, 11 Nov 2007 21:21:30 +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> <47375195.9060400@gentoo.org> <20071111190803.0f7db931@blueyonder.co.uk> In-Reply-To: <20071111190803.0f7db931@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="------------enigD98CEA9D8EE598A998448CE5" X-Archives-Salt: 72d3e9f9-b9c6-46fe-8069-3cc6f727c2e5 X-Archives-Hash: 10a584a90c330fe90894f1921b4021d0 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD98CEA9D8EE598A998448CE5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ciaran McCreesh kirjoitti: > On Sun, 11 Nov 2007 21:01:41 +0200 > Petteri R=C3=A4ty wrote: >> 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. >=20 > Neither EAPI 0 nor EAPI 1 provide any mechanism for an ebuild to 'die' > at global scope. There's simply no way for eclasses to complain that > they're being misused. >=20 Well nothing formal but the ebuild developer should pick up ewarn/echo /whatever messages coming from global scope. That's what we have in debug.eclass atm. Regards, Petteri --------------enigD98CEA9D8EE598A998448CE5 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 iD8DBQFHN1Y8cxLzpIGCsLQRAu43AJ9qjegSLG95k8fgvFomqdBOMwZN7ACgilfD zQUkfg8aelHXnJOcWKjhZXM= =kJFK -----END PGP SIGNATURE----- --------------enigD98CEA9D8EE598A998448CE5-- -- gentoo-dev@gentoo.org mailing list