Some time ago I've adopted modem-manager-gui. Recently upstream has released a new version, and while packaging this new version, I noticed a couple of issues: 1) mmgui can work with a couple of backends (different modem managers and connection managers). Each backend module is compiled into a different .so and they're all included in the package. mmgui is smart enough to recognize that a module cannot be used because it's appropriate daemon isn't running, so this isn't a problem by itself. The issue is: the new mmgui version also ships with an ofono plugin and a NetworkManager dispatcher.d script. Shipping these files without having a Requires: on ofono and NM seems dirty to me, but then - requiring all the possible backends would pull in unnecessary packages. I could separate the backends into individual packages, but I wonder - how the handle the dependencies, then? What I'd like to achieve is that one of the backends is the "recommended" one, while the others are optional. I'm not very accustomed to the weak dependencies mechanism, so I wonder: would something like "Recommends: mmgui-modemmanager; Suggests: mmgui-ofono mmgui-some_other_ backend" suffice? 2) Both the old and the new version install a polkit policy (in /usr/share/polkit-1/actions). fedora-review says that even with a "Requires: polkit", the directories have no known owners. 3) Similarly to the above - the package installs some help files in /usr/share/help. These are available in a couple languages. fedora-review says that some of the language directories (like /usr/share/help/pl) are unowned. I ran "dnf provides" and it looks like a few other packages that ship help files simply declare themselves are owning these directories. Should I do the same? _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
