Last blocker is pyside2+6 to enable py3.12 on QtPy which is needed
by pytest-qt, but tests on pyside are restricted and I do not
use/follow either of these to be able to know if it works.
If ignore the pyside deps and force enable 3.12 just to be able
to run qutebrowser's tests, it passes fine.
Leaving this on hold for now so don't need to restrict tests.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Also add the missing dependencies on qtnetwork:5 and qtwidgets:5
while revbumping. They technically cannot be missed as they are
pulled by PyQt5[network,widgets], but this is to be proper given
it's directly linked with these.
Note these could be optional (like they are in PyQt6-WebEngine behind
IUSE=+widgets), but not going to bother changing this at this point
unless someone needs this.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Not 100% sure that there is no issues with py3.12 (no test suite),
but its major revdep (qutebrowser[-qt6]) seems to be working as
expected and has no tests regressions (that is, if we force in
pytest-qt to use 3.12 despite lacking pyside's 3.12 -- pyside
won't matter for PyQt)
Also migrate to PEP517 and bring a bit more in-line with PyQt6's
ebuild (allows a fair amount of simplification). Note that migration
is based on current ebuild options and have not reviewed their
original correctness (same for dependencies), merely checked that
files install the same. Could still be oversights given the amount
of options.
wrt files, there is one difference, just like PyQt6 there is two
plugins that upstream (intentionally) does not install when using
wheels as such they are now missing, aka:
* FILES:-usr/lib64/qt5/plugins/PyQt5/libpyqt5qmlplugin.so
* FILES:-usr/lib64/qt5/plugins/designer/libpyqt5.so
Unknown if anything actually needed those with PyQt5, may need
manual handling if something comes up.
Note that I don't really plan to maintain this unless it's causing
problems, ultimately support for Qt5 will be dropped sooner than
later in qutebrowser.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Also sync small style/comment changes with PyQt6's ebuild, meant
to do this on a bump like PyQt6 but this is still the latest.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
No tests provided like other packages from this chain from this
upstream, so using qutebrowser[qt6]'s tests as reference to know
if it works with py3.12.
qutebrowser did have 3.12 issues with 6.5.1, which got fixed in
6.5.2 -- so from this assuming that the chain's latest versions
have likely been tested by upstream with 3.12 now and should be
mostly safe to add.
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Without this, _FORTIFY_SOURCE now gets undefined.
With it (but without an explicit value), glibc picks the maximum supported
number (on current toolchain 3).
Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org>