diff options
| author | Quentin Schulz <quentin.schulz@cherry.de> | 2024-08-21 18:33:09 +0200 |
|---|---|---|
| committer | Khem Raj <raj.khem@gmail.com> | 2024-08-21 12:06:12 -0700 |
| commit | 21a87a422cb3144574af20463bce33f8d9c546d2 (patch) | |
| tree | 29ecdcb31d3e5108c4217d7783f6c7b950dd4df6 /meta-python/recipes-devtools/python/python3-inotify/new-test-inotify.patch | |
| parent | 990955ba0941f207b5f4c9ead9f316c4afb5c6b9 (diff) | |
| download | meta-openembedded-21a87a422cb3144574af20463bce33f8d9c546d2.tar.gz | |
nftables: fix pep517-backend warning
nftables has a pyproject.toml file since v1.0.9, c.f.
https://git.netfilter.org/nftables/commit/?id=8e603e0f7eec7c0000344a004228a30fbf0ece5c
Styhead has started to complain when a recipe inherits setuptools3 and a
proper pyproject.toml is provided in sources.
This uses python_pep517 functions instead of the setuptools3 ones,
inherits the proper class (still using setuptools3 but through pep517
process).
Notably, the python PACKAGECONFIG has its build dependency on
python3-setuptools-native removed as it's brought in by
python_setuptools_build_meta inherit, which is performed whenever the
python PACKAGECONFIG is selected. This avoids a "duplicate" but no
change in behavior is expected.
This was only build tested.
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Diffstat (limited to 'meta-python/recipes-devtools/python/python3-inotify/new-test-inotify.patch')
0 files changed, 0 insertions, 0 deletions