additional python deps for frescobaldi
Hi, I maintain frescobaldi and recently a new version was released. It added an additional python dependency, which is not present at the moment: qpageview. I have a package ready, but which is best development project to submit this to. Related to this is a question about other python dependencies of frescobaldi. 1. python-poppler-qt5 lives in multimedia:apps. I think frescobaldi is the only one using it. Should it move to another project that has python packages? 2. python-ly was split of from frescobaldi, but I have kept it inside the frescobaldi package. I want to split this of into its own package in the future and for that I also need a home. 3. frescobaldi is also a python program, but because it's an editor for lilypond multimedia:apps seems to be a good project for it. It does not use that multi-python packaging stuff. Or should it move? What is the best thing to do here? Thanks in advance for the help. Cor
Hello Cor, Am Freitag, 6. Mai 2022, 16:52:41 CEST schrieb Cor Blom:
I maintain frescobaldi and recently a new version was released. It added an additional python dependency, which is not present at the moment: qpageview. I have a package ready, but which is best development project to submit this to.
It is a python-package from pypi, the naming convention (in case it should go to devel:languages:python is python-<pypi-name>, means python-qpageview
Related to this is a question about other python dependencies of frescobaldi.
1. python-poppler-qt5 lives in multimedia:apps. I think frescobaldi is the only one using it. Should it move to another project that has python packages?
As it is the devel repo for Factory for this package, it probably makes sense to keep it there (and python-qpageview as well)
2. python-ly was split of from frescobaldi, but I have kept it inside the frescobaldi package. I want to split this of into its own package in the future and for that I also need a home.
It makes probably sense to have a sandpit in your home:cornelisbb Project where you collect all build dependencies (as they might not be yet in Factory or Leap) and from where you submit to multimedia:apps
3. frescobaldi is also a python program, but because it's an editor for lilypond multimedia:apps seems to be a good project for it. It does not use that multi-python packaging stuff. Or should it move?
multimedia:apps seems to be a good choice Regarding singlespec: It looks to me the package is targeted for end users who will probably not install a python specific version of it. They will go for the default version. In similar situations, my choice was 'no': just build against the distribution default python. HTH Axel
Am 06.05.22 um 17:13 schrieb Axel Braun:
Hello Cor,
Am Freitag, 6. Mai 2022, 16:52:41 CEST schrieb Cor Blom:
I maintain frescobaldi and recently a new version was released. It added an additional python dependency, which is not present at the moment: qpageview. I have a package ready, but which is best development project to submit this to. It is a python-package from pypi, the naming convention (in case it should go to devel:languages:python is python-<pypi-name>, means python-qpageview
Related to this is a question about other python dependencies of frescobaldi.
1. python-poppler-qt5 lives in multimedia:apps. I think frescobaldi is the only one using it. Should it move to another project that has python packages? As it is the devel repo for Factory for this package, it probably makes sense to keep it there (and python-qpageview as well)
- multimedia:apps is fine. It has been repeatedly stated by some that devel:languages:python should cease to be a catchall, but others state the opposite. No need to get into that right now, just leave it where it is. - python-poppler-qt5 is also usable as leaf package on its own. I use it for a private project of mine.
2. python-ly was split of from frescobaldi, but I have kept it inside the frescobaldi package. I want to split this of into its own package in the future and for that I also need a home. It makes probably sense to have a sandpit in your home:cornelisbb Project where you collect all build dependencies (as they might not be yet in Factory or Leap) and from where you submit to multimedia:apps
Same es above, agree with Axel.
3. frescobaldi is also a python program, but because it's an editor for lilypond multimedia:apps seems to be a good project for it. It does not use that multi-python packaging stuff. Or should it move? multimedia:apps seems to be a good choice Regarding singlespec: It looks to me the package is targeted for end users who will probably not install a python specific version of it. They will go for the default version.
In similar situations, my choice was 'no': just build against the distribution default python.
Yes. Only use singlespec if it is to be used as a library by other singlespec packages.
HTH Axel
- Ben
participants (3)
-
Axel Braun -
Ben Greiner -
Cor Blom