| 1 |
Mike Auty wrote: |
| 2 |
> The speed issues aren't really a concern, since the GLEP suggests that |
| 3 |
> the ebuild must be sourced anyway. The GLEP allows for a .ebuild-2 file |
| 4 |
> to contain EAPI="1". |
| 5 |
|
| 6 |
Wrong. From the GLEP: "note that one should *never* explicitly set both |
| 7 |
EAPIs to different values." |
| 8 |
|
| 9 |
Basically, you don't set the post-source EAPI. It is only supposed to be |
| 10 |
used when the pre-source EAPI cannot be determined. This is entirely for |
| 11 |
backwards compatability with EAPI={0,1}. Once people start using |
| 12 |
suffixed EAPIs, EAPI should not (probably "must not") be set in the |
| 13 |
ebuild. Sure, because of how the algorithm works, people could |
| 14 |
potentially do both, but the GLEP makes it pretty clear that they shouldn't. |
| 15 |
|
| 16 |
-- |
| 17 |
Mike Kelly |
| 18 |
-- |
| 19 |
gentoo-dev@l.g.o mailing list |
Archives