| 1 |
>>>>> On Thu, 01 Nov 2018, Andrew Savchenko wrote: |
| 2 |
|
| 3 |
> -inherit eutils toolchain-funcs |
| 4 |
> +inherit toolchain-funcs |
| 5 |
> +case ${EAPI:-0} in |
| 6 |
> + # not used in the eclass, but left for backward compatibility with legacy users |
| 7 |
> + 4|5|6) inherit eutils ;; |
| 8 |
> + 7) ;; |
| 9 |
> + *) die "EAPI=${EAPI} is not supported" ;; |
| 10 |
> +esac |
| 11 |
> |
| 12 |
> case ${EAPI:-0} in |
| 13 |
> - 4|5|6) EXPORT_FUNCTIONS pkg_setup ;; |
| 14 |
> + 4|5|6|7) EXPORT_FUNCTIONS pkg_setup ;; |
| 15 |
> *) die "EAPI=${EAPI} is not supported" ;; |
| 16 |
> esac |
| 17 |
|
| 18 |
Why is the second case statement needed? Program flow can only reach it |
| 19 |
if the EAPI is 4, 5, 6, or 7. |
| 20 |
|
| 21 |
Ulrich |
Archives