| 1 |
> |
| 2 |
> -inherit eutils toolchain-funcs |
| 3 |
> +inherit toolchain-funcs |
| 4 |
> |
| 5 |
> case ${EAPI:-0} in |
| 6 |
> - 4|5|6) EXPORT_FUNCTIONS pkg_setup ;; |
| 7 |
> + 4|5|6|7) EXPORT_FUNCTIONS pkg_setup ;; |
| 8 |
> *) die "EAPI=${EAPI} is not supported" ;; |
| 9 |
> esac |
| 10 |
> |
| 11 |
|
| 12 |
^ The disadvantage of this is that eutils inheritance then suddenly disappears |
| 13 |
for all ebuilds. And you don't know who assumed implicitly somewhere that |
| 14 |
inheriting fortran-2 makes epatch available... |
| 15 |
|
| 16 |
So how about still inheriting eutils for EAPI 4,5,6 and only dropping it for |
| 17 |
EAPI 7 ?! |
| 18 |
|
| 19 |
|
| 20 |
-- |
| 21 |
Andreas K. Hüttel |
| 22 |
dilfridge@g.o |
| 23 |
Gentoo Linux developer |
| 24 |
(council, toolchain, perl, libreoffice, comrel) |
Archives