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