>>>>> On Tue, 06 Oct 2020, William Hubbs wrote:
>> +case "${EAPI:-0}" in
>> + 0|1|2|3|4|5|6)
>> + die "Unsupported EAPI=${EAPI} (obsolete) for ${ECLASS}"
>> + ;;
>> + 7)
>> + ;;
>> + *)
>> + die "Unsupported EAPI=${EAPI} (unknown) for ${ECLASS}"
>> + ;;
>> +esac
> Does it really matter that an EAPI is unsupported because it is
> obsolete vs unknown? Can we simplify this case statement to the
> following or something similar for all of our eclasses?
> case "${EAPI:-0}" in
> 7)
> ;;
> *)
> die "Unsupported EAPI=${EAPI} (unknown) for ${ECLASS}"
> ;;
> esac
I am with you there, at least for a new eclass that never supported
these old EAPIs.
It may be somewhat useful when removing existing support for an EAPI,
but even there things should be clear from context?
Ulrich
signature.asc
Description: PGP signature
