| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On 20-07-2010 04:55, Alexis Ballier wrote: |
| 5 |
> On Sunday 18 July 2010 04:54:43 Jorge Manuel B. S. Vicetto wrote: |
| 6 |
>> On 18-07-2010 00:58, Brian Harring wrote: |
| 7 |
>>> On Sun, Jul 18, 2010 at 02:56:05AM +0300, Alexis Ballier wrote: |
| 8 |
>>>> case ${EAPI:-0} in |
| 9 |
>>>> |
| 10 |
>>>> 2|3|4) ;; |
| 11 |
>>>> *) DEPEND="EAPI-TOO-OLD" ;; |
| 12 |
>>>> |
| 13 |
>>>> esac |
| 14 |
>>>> |
| 15 |
>>>> why not: |
| 16 |
>>>> |
| 17 |
>>>> case ${EAPI:-0} in |
| 18 |
>>>> |
| 19 |
>>>> 0|1) DEPEND="EAPI-TOO-OLD" ;; |
| 20 |
>>>> |
| 21 |
>>>> esac |
| 22 |
>> |
| 23 |
>> Alexis, |
| 24 |
>> |
| 25 |
>> the problem with your alternative is that it's "too clever" and won't |
| 26 |
>> die/kill/stop the processing of the eclass for newer EAPIs that at any |
| 27 |
>> point in time no one can be sure will be compatible with the current |
| 28 |
>> eclass design. |
| 29 |
>> That's why it has been agreed that eclasses should specifically list all |
| 30 |
>> supported EAPI versions and die/kill/stop on all other EAPI versions. |
| 31 |
> |
| 32 |
> Fair enough. Why is EAPI 4 in that list then ? Has it been approved/finalized |
| 33 |
> yet ? |
| 34 |
|
| 35 |
You raise an important point that had slipped my reading. |
| 36 |
EAPI-4 spec was approved by the council some time ago. Actually it was |
| 37 |
EAPI-3, but then there was a decision to get EAPI-3 as EAPI-2 + prefix |
| 38 |
support and use the approved spec for EAPI-4. |
| 39 |
However, the EAPI-4 spec is still pending Portage implementation and |
| 40 |
thus it's my opinion that no eclass in the tree should state |
| 41 |
compatibility with it as we don't want eclasses claiming compatibility |
| 42 |
with an EAPI that is yet to be implemented. |
| 43 |
|
| 44 |
> Alexis. |
| 45 |
> |
| 46 |
|
| 47 |
- -- |
| 48 |
Regards, |
| 49 |
|
| 50 |
Jorge Vicetto (jmbsvicetto) - jmbsvicetto at gentoo dot org |
| 51 |
Gentoo- forums / Userrel / Devrel / KDE / Elections |
| 52 |
-----BEGIN PGP SIGNATURE----- |
| 53 |
Version: GnuPG v2.0.16 (GNU/Linux) |
| 54 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 55 |
|
| 56 |
iQIcBAEBAgAGBQJMRW29AAoJEC8ZTXQF1qEPzmgQAJ4X4r7n4PN0egqYAe/1cuJp |
| 57 |
LtLQqQnL0CWkZIKp4k3ygGm9GolOJ7glB4FWkak9XcXoioyY6fU5hNY9rDAphjM4 |
| 58 |
8EcMeF2gTD1obiqPJps+dwU83vRRh9QzyvxXMRaqZc3n2ydvOXpH3G9/uJ3sv7y7 |
| 59 |
uBY0UnCGPg8IyaciEBuruNHb4uJsbGdORJvqFRgGTWR6FwdXV7tOWpL185mz8qja |
| 60 |
akDAA5pjcmmVbJmAANfWOrYzc+05lCKFsNTfoDiZEs7awtDmsoxcS0pKy/XJ7iLl |
| 61 |
hc/dVC2DquOpC6qOM8oTulxzGnfCLDlQ+hlIihbFhMjMUyzyLn2APA3GAUQdz76d |
| 62 |
dmp8VqLQrXKDVh8GtYZyrkA8yiD18R8GT427v0NdMQpG+5fi2UqHqRBHZCE1Z+Vq |
| 63 |
gnPRekTdpPTGJE8CcLgt+LzG8j7lP+omS9hT8TRYOQXvM34XVKOo1h7kw5nXYll1 |
| 64 |
exqYQmGo9FeT5Fn5eSdgquqJP83WIIf+Fi6hhegYeTPDyYmRnilFCDmw4tt5S5fI |
| 65 |
Ta16FwIwmK5G6DHdz/OK+wlcWrMC2iKHcll8oowHfobvPBD5vEyl16ln7WFkgf4q |
| 66 |
TabMxk8ImTTQvEQcE829vTExtwqwoJ3JPrFmR5g4EQ7Re9f2ngZ89jz1fTyQYz9R |
| 67 |
pLUXQfw8Jg9qc1JypqaU |
| 68 |
=hMJr |
| 69 |
-----END PGP SIGNATURE----- |
Archives