| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Mike Kelly wrote: |
| 5 |
| Wrong. |
| 6 |
|
| 7 |
Thanks for that. I'm gonna assume you meant "I think you're wrong". |
| 8 |
|
| 9 |
| Sure, because of how the algorithm works, people could potentially do |
| 10 |
| both, but the GLEP makes it pretty clear that they shouldn't. |
| 11 |
|
| 12 |
It doesn't just say they shouldn't, it *says what happens if they do*: |
| 13 |
|
| 14 |
pkg-4.ebuild-2, EAPI="1" |
| 15 |
|
| 16 |
~ pre-source EAPI is 2, post-source EAPI is 1. EAPI 1 is used |
| 17 |
|
| 18 |
So to live up to the GLEP specification, package managers must source |
| 19 |
the ebuild to determine the correct EAPI. |
| 20 |
|
| 21 |
| Basically, you don't set the post-source EAPI. It is only supposed to |
| 22 |
| be used when the pre-source EAPI cannot be determined. |
| 23 |
|
| 24 |
If that's what was meant, the GLEP needs changing to say that. |
| 25 |
Something like: |
| 26 |
|
| 27 |
pkg-4.ebuild-2, EAPI="X" |
| 28 |
|
| 29 |
~ Pre-source EAPI is 2, post-source EAPI is X. In this instance the |
| 30 |
post-source EAPI is ignored, since a pre-source EAPI is set, so EAPI 2 |
| 31 |
is used. |
| 32 |
|
| 33 |
It's not a big deal, but it will need a change to the GLEP in its |
| 34 |
current form, if that's what's meant. |
| 35 |
|
| 36 |
Mike 5:) |
| 37 |
-----BEGIN PGP SIGNATURE----- |
| 38 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 39 |
|
| 40 |
iEYEARECAAYFAkhPdRUACgkQu7rWomwgFXq1twCgqnFzBqQI8vl63faZ1cq27MF7 |
| 41 |
7ekAn0aA73nic1v/ovwAUuHsaL44MrTE |
| 42 |
=StC2 |
| 43 |
-----END PGP SIGNATURE----- |
| 44 |
-- |
| 45 |
gentoo-dev@l.g.o mailing list |
Archives