summaryrefslogtreecommitdiff
path: root/dev-qt/qtwebengine/files
diff options
context:
space:
mode:
authorSam James <sam@gentoo.org>2025-03-31 16:47:41 +0100
committerSam James <sam@gentoo.org>2025-03-31 16:52:41 +0100
commitc3315537514a3457b3a43674bfe721aa4cff110e (patch)
tree75a9a4d3c54492d0bfe23c39cf931fb4f0bb403f /dev-qt/qtwebengine/files
parentbf7042411b580d3e36b7f29a568d4ccde18726c7 (diff)
downloadgentoo-c3315537514a3457b3a43674bfe721aa4cff110e.tar.gz
gentoo-c3315537514a3457b3a43674bfe721aa4cff110e.tar.bz2
gentoo-c3315537514a3457b3a43674bfe721aa4cff110e.zip
net-analyzer/fail2ban: port to python-single-r1
The package isn't suitable for PEP517, as it installs data files and it simply happens to be written in Python, rather than intending to be imported and so on. Unfortunately, for the remaining PEP517 holdouts, there's little pressure upstream for them to port to a proper build system yet, as while setuptools deprecated the `setup.py` entrypoint some time ago, there's no removal in sight yet, so the only pressing side is on Gentoo's where we want to cleanup distutils-r1's support for that. It was arguably a mistake to really have these packages use distutils-r1 in the first place. The obvious workaround for now is to invoke setup.py manually w/ python-single-r1, and punt the question until setuptools removal of the entrypoint looks closer (at which time, other distros will be putting pressure on upstreams too). Of course, if at the time of such a setuptools change, the package is still not fixed, then we'd have to remove it. (The same issues apply to bug #923080 which isn't fixed by this, but hopefully won't be an actual problem until that aforementioned removal in setuptools itself of the other bits.) Bug: https://bugs.gentoo.org/923080 Closes: https://bugs.gentoo.org/909998 Signed-off-by: Sam James <sam@gentoo.org>
Diffstat (limited to 'dev-qt/qtwebengine/files')
0 files changed, 0 insertions, 0 deletions