| 1 |
On Tue, 31 May 2011 15:07:17 -0400 |
| 2 |
Mike Gilbert <floppymaster@×××××.com> wrote: |
| 3 |
|
| 4 |
> case ${EAPI:-0} in |
| 5 |
> 0|1) die "EAPI ${EAPI} unsupported.";; |
| 6 |
> 2|3|4) ;; |
| 7 |
> *) die "github-snapshot.eclass API in EAPI ${EAPI} not yet |
| 8 |
> established." esac |
| 9 |
> |
| 10 |
> Why are EAPI 0 and 1 unsupported? I don't see anything that would need |
| 11 |
> EAPI 2 features. |
| 12 |
|
| 13 |
I don't see a reason to support them. They don't provide src_prepare() |
| 14 |
which increases amount of code required by user to handle them. |
| 15 |
Moreover, github snapshots require EAPI2 arrows in SRC_URI anyway. |
| 16 |
|
| 17 |
-- |
| 18 |
Best regards, |
| 19 |
Michał Górny |
Archives