May 24, 2019 11:39 AM, "David Seifert" <[email protected]> wrote:
> +case ${EAPI} in
> + [4-7]) ;;
> + *) die "EAPI=${EAPI:-0} is not supported" ;;
> +esac
> +
Hi,
I often wondered, why using a eapi-whitelisting logic instead of
eapi-blacklisting?
This kind of change forces to touch the eclass for the next eapi bump, while
being a more defensive
writing style, is it really needed?
Best regards,
Corentin “Nado” Pazdera
