RFC: New devel project devel:languages:python:pyqt and deal with different SIP versions
Hello, python-sip, python-qt5 and co. have always been kind of a foreign body to C++ focused KDE:Qt5. May I propose to create devel:languages:python:pyqt and put related packages into that one? Maintainers could be python and QT/KDE people together. ## List of existing packages to be considered: python-pyqt-builder python-pyqt-rpm-macros python-qt3d-qt5 python-qt5 python-qt5-sip python-qtcharts-qt5 python-qtdatavis3d-qt5 python-qtwebengine-qt5 python-sip python-sip4 qscintilla-qt5 ## New packages to be created (using the PyPI names as naming template instead of continuing the legacy rpm package names. Of course appropriate `Provides:` tags for the rpm names should be included): python-PyQt6 (also providing python-qt6) python-PyQt6-sip (also providing python-qt6-sip) python-PyQt6-3D (also providing python-qt3d-qt6) python-PyQt6-NetworkAuth (also providing python-networkauth-qt6) python-sip6 (see below) ... and more of the family as they are released upstream. ## Not PyQt[56] but closely related or the "competitor": python-PySide6 python-PySide2 (currently python3-pyside2) python-QtAwesome python-QtPy python-poppler-qt5 qutebrowser eric ... There is also SIP v6 now. Some packages still depend on SIP v4 (e.g. cura libraries) or use the legacy features of SIP v5 (e.g. the sip5 executable), so we can't just have a single up to date python-sip. After some discussion with DimStar a few days ago, I propose, what I call the "tornado approach", because it is what python-tornado is doing right now: * Have python-sip4, python-sip5, python-sip6, all providing python-sip * Make python-sip a meta package and have it require the currently preferred default (python-sip5 at the moment). * Have the appropriate `Prefer:` tags in prjconf. Thoughts and comments welcome! Ben
Am 19.02.21 um 20:48 schrieb Ben Greiner:
Hello,
python-sip, python-qt5 and co. have always been kind of a foreign body to C++ focused KDE:Qt5. May I propose to create devel:languages:python:pyqt and put related packages into that one? Maintainers could be python and QT/KDE people together.
## List of existing packages to be considered:
python-pyqt-builder python-pyqt-rpm-macros python-qt3d-qt5 python-qt5 python-qt5-sip python-qtcharts-qt5 python-qtdatavis3d-qt5 python-qtwebengine-qt5 python-sip python-sip4 qscintilla-qt5
## New packages to be created (using the PyPI names as naming template instead of continuing the legacy rpm package names. Of course appropriate `Provides:` tags for the rpm names should be included):
python-PyQt6 (also providing python-qt6) python-PyQt6-sip (also providing python-qt6-sip) python-PyQt6-3D (also providing python-qt3d-qt6) python-PyQt6-NetworkAuth (also providing python-networkauth-qt6) python-sip6 (see below) ... and more of the family as they are released upstream.
[...]
There is also SIP v6 now. Some packages still depend on SIP v4 (e.g. cura libraries) or use the legacy features of SIP v5 (e.g. the sip5 executable), so we can't just have a single up to date python-sip. After some discussion with DimStar a few days ago, I propose, what I call the "tornado approach", because it is what python-tornado is doing right now:
* Have python-sip4, python-sip5, python-sip6, all providing python-sip * Make python-sip a meta package and have it require the currently preferred default (python-sip5 at the moment). * Have the appropriate `Prefer:` tags in prjconf.
Here is a demo project implementing it: https://build.opensuse.org/project/show/home:bnavigator:pyqt
Thoughts and comments welcome!
Ben
Hi, Firstly Cross posting to factory as there is a chance not everyone who needs to read this is on packaging@ (more for packaging help and support) On 2/20/21 6:18 AM, Ben Greiner wrote:
Hello,
python-sip, python-qt5 and co. have always been kind of a foreign body to C++ focused KDE:Qt5. May I propose to create devel:languages:python:pyqt and put related packages into that one? Maintainers could be python and QT/KDE people together.
Its worth noting that currently python-qt etc is staged and bought up with each Qt version https://build.opensuse.org/package/show/KDE:Qt:5.15/python-qt5 for example so how well this change will work with the existing Qt setup I guess we will have to wait for the KDE/Qt people to answer.
## List of existing packages to be considered:
python-pyqt-builder python-pyqt-rpm-macros python-qt3d-qt5 python-qt5 python-qt5-sip python-qtcharts-qt5 python-qtdatavis3d-qt5 python-qtwebengine-qt5 python-sip python-sip4 qscintilla-qt5
## New packages to be created (using the PyPI names as naming template instead of continuing the legacy rpm package names. Of course appropriate `Provides:` tags for the rpm names should be included):
python-PyQt6 (also providing python-qt6) python-PyQt6-sip (also providing python-qt6-sip) python-PyQt6-3D (also providing python-qt3d-qt6) python-PyQt6-NetworkAuth (also providing python-networkauth-qt6) python-sip6 (see below) ... and more of the family as they are released upstream.
## Not PyQt[56] but closely related or the "competitor":
python-PySide6 python-PySide2 (currently python3-pyside2) python-QtAwesome python-QtPy python-poppler-qt5 qutebrowser eric ...
There is also SIP v6 now. Some packages still depend on SIP v4 (e.g. cura libraries) or use the legacy features of SIP v5 (e.g. the sip5 executable), so we can't just have a single up to date python-sip. After some discussion with DimStar a few days ago, I propose, what I call the "tornado approach", because it is what python-tornado is doing right now:
* Have python-sip4, python-sip5, python-sip6, all providing python-sip * Make python-sip a meta package and have it require the currently preferred default (python-sip5 at the moment). * Have the appropriate `Prefer:` tags in prjconf.
Thoughts and comments welcome!
Ben
-- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
Am 21.02.21 um 13:30 schrieb Simon Lees:
Hi,
Firstly Cross posting to factory as there is a chance not everyone who needs to read this is on packaging@ (more for packaging help and support)
In this case the instructions in the project description of devel:languages:python need an update and an appropriate mention of the factory mailing list in the wiki [1] should be added.
On 2/20/21 6:18 AM, Ben Greiner wrote:
Hello,
python-sip, python-qt5 and co. have always been kind of a foreign body to C++ focused KDE:Qt5. May I propose to create devel:languages:python:pyqt and put related packages into that one? Maintainers could be python and QT/KDE people together. Its worth noting that currently python-qt etc is staged and bought up with each Qt version https://build.opensuse.org/package/show/KDE:Qt:5.15/python-qt5 for example so how well this change will work with the existing Qt setup I guess we will have to wait for the KDE/Qt people to answer.
It's a long standing myth, but not true [2, 3]. And of course all those subprojects can continue to link to their preferred package version. Strangely, many Qt5 packages in Factory don't even have an assigned devel project at all [4]. python-qt5 has devel project KDE:Qt5, btw.
## List of existing packages to be considered:
python-pyqt-builder python-pyqt-rpm-macros python-qt3d-qt5 python-qt5 python-qt5-sip python-qtcharts-qt5 python-qtdatavis3d-qt5 python-qtwebengine-qt5 python-sip python-sip4 qscintilla-qt5
## New packages to be created (using the PyPI names as naming template instead of continuing the legacy rpm package names. Of course appropriate `Provides:` tags for the rpm names should be included):
python-PyQt6 (also providing python-qt6) python-PyQt6-sip (also providing python-qt6-sip) python-PyQt6-3D (also providing python-qt3d-qt6) python-PyQt6-NetworkAuth (also providing python-networkauth-qt6) python-sip6 (see below) ... and more of the family as they are released upstream.
## Not PyQt[56] but closely related or the "competitor":
python-PySide6 python-PySide2 (currently python3-pyside2) python-QtAwesome python-QtPy python-poppler-qt5 qutebrowser eric ...
There is also SIP v6 now. Some packages still depend on SIP v4 (e.g. cura libraries) or use the legacy features of SIP v5 (e.g. the sip5 executable), so we can't just have a single up to date python-sip. After some discussion with DimStar a few days ago, I propose, what I call the "tornado approach", because it is what python-tornado is doing right now:
* Have python-sip4, python-sip5, python-sip6, all providing python-sip * Make python-sip a meta package and have it require the currently preferred default (python-sip5 at the moment). * Have the appropriate `Prefer:` tags in prjconf.
Thoughts and comments welcome!
Ben
Cheers, Ben [1] https://en.opensuse.org/openSUSE:How_to_contribute_to_Factory#How_to_request... [2] https://www.riverbankcomputing.com/static/Docs/PyQt5/installation.html#under... [3] https://www.riverbankcomputing.com/static/Docs/PyQt6/installation.html#under... [3] https://build.opensuse.org/project/show/KDE:Qt:5.15#comment-1286381
Am 21.02.21 um 13:30 schrieb Simon Lees:
Hi,
Firstly Cross posting to factory as there is a chance not everyone who needs to read this is on packaging@ (more for packaging help and support)
In this case the instructions in the project description of devel:languages:python need an update and an appropriate mention of the factory mailing list in the wiki [1] should be added. **** ... and of course I hit the send button with the wrong sender tag again, so if a moderator decides to let that through instead of discarding, you get this mail up to 4 times now m-( Sorry. *****
On 2/20/21 6:18 AM, Ben Greiner wrote:
Hello,
python-sip, python-qt5 and co. have always been kind of a foreign body to C++ focused KDE:Qt5. May I propose to create devel:languages:python:pyqt and put related packages into that one? Maintainers could be python and QT/KDE people together. Its worth noting that currently python-qt etc is staged and bought up with each Qt version https://build.opensuse.org/package/show/KDE:Qt:5.15/python-qt5 for example so how well this change will work with the existing Qt setup I guess we will have to wait for the KDE/Qt people to answer.
It's a long standing myth, but not true [2, 3]. And of course all those subprojects can continue to link to their preferred package version. Strangely, many Qt5 packages in Factory don't even have an assigned devel project at all [4]. python-qt5 has devel project KDE:Qt5, btw.
## List of existing packages to be considered:
python-pyqt-builder python-pyqt-rpm-macros python-qt3d-qt5 python-qt5 python-qt5-sip python-qtcharts-qt5 python-qtdatavis3d-qt5 python-qtwebengine-qt5 python-sip python-sip4 qscintilla-qt5
## New packages to be created (using the PyPI names as naming template instead of continuing the legacy rpm package names. Of course appropriate `Provides:` tags for the rpm names should be included):
python-PyQt6 (also providing python-qt6) python-PyQt6-sip (also providing python-qt6-sip) python-PyQt6-3D (also providing python-qt3d-qt6) python-PyQt6-NetworkAuth (also providing python-networkauth-qt6) python-sip6 (see below) ... and more of the family as they are released upstream.
## Not PyQt[56] but closely related or the "competitor":
python-PySide6 python-PySide2 (currently python3-pyside2) python-QtAwesome python-QtPy python-poppler-qt5 qutebrowser eric ...
There is also SIP v6 now. Some packages still depend on SIP v4 (e.g. cura libraries) or use the legacy features of SIP v5 (e.g. the sip5 executable), so we can't just have a single up to date python-sip. After some discussion with DimStar a few days ago, I propose, what I call the "tornado approach", because it is what python-tornado is doing right now:
* Have python-sip4, python-sip5, python-sip6, all providing python-sip * Make python-sip a meta package and have it require the currently preferred default (python-sip5 at the moment). * Have the appropriate `Prefer:` tags in prjconf.
Thoughts and comments welcome!
Ben
Cheers, Ben [1] https://en.opensuse.org/openSUSE:How_to_contribute_to_Factory#How_to_request... [2] https://www.riverbankcomputing.com/static/Docs/PyQt5/installation.html#under... [3] https://www.riverbankcomputing.com/static/Docs/PyQt6/installation.html#under... [3] https://build.opensuse.org/project/show/KDE:Qt:5.15#comment-1286381
On 2/22/21 1:36 AM, Ben Greiner wrote:
Am 21.02.21 um 13:30 schrieb Simon Lees:
Hi,
Firstly Cross posting to factory as there is a chance not everyone who needs to read this is on packaging@ (more for packaging help and support)
In this case the instructions in the project description of devel:languages:python need an update and an appropriate mention of the factory mailing list in the wiki [1] should be added.
Yeah that project description seems wrong, especially now that we have a dedicated python mailing list which can be used for python specific things. But factory is the mailing list where all the developers working on openSUSE in general are so its the best place for questions and discussions that involve multiple parts of the distro. The wiki page already mentions the following, if you have a better wording or can suggest a change let me know and i'm happy to make it. === Whether or not you have edit permissions on the package, you can trigger a submit request of the package to openSUSE:Factory. That submit request should contain a note with information about the package. Preferably, you introduce the package to the opensuse-factory list and point to that introduction in your submitrequest. A good introduction contains information on the state of the upstream project and how maintainable it is and what the purpose of having it in the distribution will be. === -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On 22.02.21 00:11, Simon Lees wrote:
On 2/22/21 1:36 AM, Ben Greiner wrote:
Am 21.02.21 um 13:30 schrieb Simon Lees:
Hi,
Firstly Cross posting to factory as there is a chance not everyone who needs to read this is on packaging@ (more for packaging help and support) Further discussion is in factory@ only.
In data domenica 21 febbraio 2021 13:30:56 CET, Simon Lees ha scritto: Hello,
example so how well this change will work with the existing Qt setup I guess we will have to wait for the KDE/Qt people to answer.
If I understood this correctly, this means a new devel project *exclusively* for PyQt stuff (while official stuff from Qt like PySide would stay there)? If that's the case, at least from me there's a +1, as improved maintenance of PyQt would definitely help. The KDE:Qt projects would just link the packages from Factory in that case. Fabian, Cristophe, are you also OK with this? -- Luca Beltrame - KDE Forums team GPG key ID: A29D259B
Op 19-02-2021 om 20:48 schreef Ben Greiner:
python-sip, python-qt5 and co. have always been kind of a foreign body to C++ focused KDE:Qt5. May I propose to create devel:languages:python:pyqt and put related packages into that one? Maintainers could be python and QT/KDE people together.
## List of existing packages to be considered:
python-pyqt-builder python-pyqt-rpm-macros python-qt3d-qt5 python-qt5 python-qt5-sip python-qtcharts-qt5 python-qtdatavis3d-qt5 python-qtwebengine-qt5 python-sip python-sip4 qscintilla-qt5
## New packages to be created (using the PyPI names as naming template instead of continuing the legacy rpm package names. Of course appropriate `Provides:` tags for the rpm names should be included):
python-PyQt6 (also providing python-qt6) python-PyQt6-sip (also providing python-qt6-sip) python-PyQt6-3D (also providing python-qt3d-qt6) python-PyQt6-NetworkAuth (also providing python-networkauth-qt6) python-sip6 (see below) ... and more of the family as they are released upstream.
## Not PyQt[56] but closely related or the "competitor":
python-PySide6 python-PySide2 (currently python3-pyside2) python-QtAwesome python-QtPy python-poppler-qt5
Is it an idea to include also python-poppler-qt5 in that new devel:languages:python:pyqt project? It now lives in multimedia:apps for the simple reason it is needed for frescobaldi, and originally frescobaldi was the only user. Frescobaldi is the reason I maintain it. Ben told me it can be interesting for other software projects. Regards, Cor
On 23.02.21 11:05, Cor Blom wrote:
Op 19-02-2021 om 20:48 schreef Ben Greiner:
## Not PyQt[56] but closely related or the "competitor":
python-poppler-qt5
Is it an idea to include also python-poppler-qt5 in that new devel:languages:python:pyqt project? It now lives in multimedia:apps for the simple reason it is needed for frescobaldi, and originally frescobaldi was the only user. Frescobaldi is the reason I maintain it. Ben told me it can be interesting for other software projects.
Regards,
Cor
Please see my reply to Luca in factory@lists.opensuse.org. python-poppler-qt5 is a pure SIP project. It could live well in d:l:p:pyqt. PySide will most likely stay in KDE:QtXX. Cheers, Ben
Dne 23. 02. 21 v 11:05 Cor Blom napsal(a):
Op 19-02-2021 om 20:48 schreef Ben Greiner:
python-sip, python-qt5 and co. have always been kind of a foreign body to C++ focused KDE:Qt5. May I propose to create devel:languages:python:pyqt and put related packages into that one? Maintainers could be python and QT/KDE people together.
I generally applaud the idea: if somebody wants to enclose away some set of packages I don't have to care about, it is always a great idea to me. Especially, if she pulls away from my reach some packages from d:l:p which I won't have to care about. The question remains however, whether it should be more d:l:p:pyqt or whether it should be KDE:Qt:Python (or something like that). Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 But if we find we have left our bones to bleach in these desert sands for nothing, beware the fury of the legions... -- Centurion in a letter home from North Africa 3rd Century
participants (6)
-
Ben Greiner -
Benjamin Greiner -
Cor Blom -
Luca Beltrame -
Matěj Cepl -
Simon Lees