On Sun, Sep 05, 2010 at 02:12:06PM +0200, Josselin Mouette wrote: > The dependency is here for two reasons: > 1. Ensuring a recent enough version is installed. This reason will > indeed cease to exist after the next release. > 2. Ensuring that gconf2 is installed on the system. > > You don’t want to end up in a situation where gconf2 is not installed, > since in this case the schemas would not be registered.
But that's exactly what I want to end up with, because no application on my system uses gconf. To clarify: mumble only uses dh_gconf to install a url-handler: --- debian/mumble.gconf-defaults --- /desktop/gnome/url-handlers/mumble/command "mumble %s" /desktop/gnome/url-handlers/mumble/needs_terminal false /desktop/gnome/url-handlers/mumble/enabled true --- So the only thing dh_gconf does as I can see, is copy this file to debian/mumble/usr/share/gconf/defaults/10_mumble. No maintainer script snippets are created. I'm not sure about the workings of gconf, but I guess if a package registers a schema, it does this because it actually uses gconf as a configuration backend, and in this case it is of course OK to add a dependency to gconf, because it would be needed in any case. dh_gconf should differentiate between these cases and only add the dependency, if it is really required. Cheers, harry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
