On Mon, 2015-03-30 at 13:57 +0200, Bruno Friedmann wrote:
For my full understanding, I still need some clarifrcation :
We have ton's of global application that can be split into several rpm. Then how it should be handled ... a specific rpm presenting just the application with all requires sub rpm?
The guideline there is: if it makes sense to have one part / .desktop file available to the user without the others, then preferably it should be split. We (GNOME Team) for example split out eog-plugins in like 10 sub packages (they don't have a .desktop file, but provide a meta file to declare to GNOME Software that the packages extend eog's functionality further... that can be introduced later though)
What about typical server package (seems strange to have a screenshot of a database module for example) Then if I create a desktop file for collectd then it will appear in the user menu. Or this kind of application/service have nothing to do with user interaction most of the time.
I'd not consider a 'server' an 'end user targeted application' that makes any sense to be presented in a Software Center. Stuff that does not have a .desktop file, should not receive one and should also not go to the Software Centers (in short: if I can't start it and interact with it, it's no application).
Thanks for your comments
Does that clarify things? Cheers, Dominique -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org