diff options
| author | Florian Schmaus <flow@gentoo.org> | 2022-02-18 09:44:13 +0100 |
|---|---|---|
| committer | Florian Schmaus <flow@gentoo.org> | 2022-02-22 08:32:18 +0100 |
| commit | 52acf58202ee276674745962306d6cb00223f5e2 (patch) | |
| tree | ca124b12473e3e0d0fcdfc352852e13a5b1fd0b4 /dev-python/bitarray/bitarray-2.3.7.ebuild | |
| parent | 17967e9fa12fde482a6a549050c883b20d99b076 (diff) | |
| download | gentoo-52acf58202ee276674745962306d6cb00223f5e2.tar.gz gentoo-52acf58202ee276674745962306d6cb00223f5e2.tar.bz2 gentoo-52acf58202ee276674745962306d6cb00223f5e2.zip | |
db-use.eclass: add support for EAPI 8, die on unknown EAPI
Add support for EAPI 8 and drop support for EAPIs < 5. Also explicitly
die on unknown EAPI values. Note that this is a deviation from the
currenty approach that the eclass uses since 86416d2c4bf1 ("eclass:
db-use - Update to eapi7-ver"). But I argue that it is confusing that
your static ananlysis tools (pkgcheck, repoman) complain about an
unsupported EAPI in an eclass, while the ebuild works just fine. While I
also think it is likely that this eclass will support future EAPI
versions without any modifications, my conclusion is that this is actually
an argument to die on unknown EAPIs, since it is trivial to bump, while
on the other hand, you never know if it really works.
Signed-off-by: Florian Schmaus <flow@gentoo.org>
Closes: https://github.com/gentoo/gentoo/pull/24246
Signed-off-by: Florian Schmaus <flow@gentoo.org>
Diffstat (limited to 'dev-python/bitarray/bitarray-2.3.7.ebuild')
0 files changed, 0 insertions, 0 deletions