Hi Frank, Am 11.05.21 um 19:14 schrieb Frank Kunz:
I try to package a multi-python application and I got the build working so far, but when adding a desktop file I get this rpmlint problems:
The package is built here: https://build.opensuse.org/package/show/home:frank_kunz/nanovna-saver
I used this package as example https://build.opensuse.org/package/show/openSUSE:Factory/python-Twisted since this has man pages handled by python_alternative and my idea was to do it the same for a desktop file. I'm not sure if python_alternative is the right way to go for desktop files, or if there is an other possibility. The python packaging wiki(https://en.opensuse.org/openSUSE:Packaging_Python) does not list that. How can I fix that problem, or, if any, what is the better way to package the desktop file?
Br, Frank
To me, NanoVNA-Saver looks like an application rather than a library of modules to be imported by other modules/applications. Making it singlespec multi-python is probably not necessary or even desired. Better create a single nanovna-saver package without the %python_subpackages generator and use python3-foo dependencies. You can still leverage the python-rpm-macros. Even python_module, if you `%define pythons python3`. If you really want to create packages for multiple python flavors, you can avoid file conflicts for the .desktop file and icon with at least two options: 1. Provide a desktop file and icon for every subpackage No need to make it u-a controlled. You will just have entries for every flavor in the application menu. sr#893151 2. Create a unflavored subpackage for the desktop file and icon. Only the u-a selected command will have a menu entry. sr#893153 HTH, Ben