Archives
Archives
| From: | "Corentin “Nado” Pazdera" <nado@××××××××××.be> | ||
|---|---|---|---|
| To: | gentoo-dev@l.g.o | ||
| Subject: | Re: [gentoo-dev] [PATCH] savedconfig.eclass: Remove old EAPI ED/EROOT workarounds | ||
| Date: | Fri, 24 May 2019 10:58:42 | ||
| Message-Id: | 85f88fa220d5a21a38ab276e5503601c@troglodyte.be | ||
| In Reply to: | [gentoo-dev] [PATCH] savedconfig.eclass: Remove old EAPI ED/EROOT workarounds by David Seifert |
||
| 1 | May 24, 2019 11:39 AM, "David Seifert" <soap@g.o> wrote: |
| 2 | |
| 3 | > +case ${EAPI} in |
| 4 | > + [4-7]) ;; |
| 5 | > + *) die "EAPI=${EAPI:-0} is not supported" ;; |
| 6 | > +esac |
| 7 | > + |
| 8 | |
| 9 | Hi, |
| 10 | |
| 11 | I often wondered, why using a eapi-whitelisting logic instead of eapi-blacklisting? |
| 12 | This kind of change forces to touch the eclass for the next eapi bump, while being a more defensive |
| 13 | writing style, is it really needed? |
| 14 | |
| 15 | Best regards, |
| 16 | Corentin “Nado” Pazdera |
| Subject | Author |
|---|---|
| Re: [gentoo-dev] [PATCH] savedconfig.eclass: Remove old EAPI ED/EROOT workarounds | David Seifert <soap@g.o> |