| 1 |
>>>>> On Fri, 02 Jul 2021, William Hubbs wrote: |
| 2 |
|
| 3 |
> case ${EAPI:-0} in |
| 4 |
|
| 5 |
This could be just ${EAPI}. |
| 6 |
|
| 7 |
> - 0|1|2|3|4|5|6) |
| 8 |
> - die "Unsupported EAPI=${EAPI} (too old) for ${ECLASS}" |
| 9 |
> - ;; |
| 10 |
> 7|8) |
| 11 |
> ;; |
| 12 |
> *) |
| 13 |
> - die "Unsupported EAPI=${EAPI} (unknown) for ${ECLASS}" |
| 14 |
> + die "Unsupported EAPI=${EAPI} for ${ECLASS}" |
| 15 |
> ;; |
| 16 |
|
| 17 |
May I suggest that we standardise the error message? Many eclasses have |
| 18 |
this (see for example toolchain-funcs.eclass): |
| 19 |
|
| 20 |
*) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;; |
| 21 |
|
| 22 |
> esac |
| 23 |
|
| 24 |
Same for the other two eclasses. |
| 25 |
|
| 26 |
Ulrich |
Archives