Hi, Le dimanche 29 août 2010 à 13:50 -0400, Joey Hess a écrit : > dh_gconf originally added dependencies on gconf2 because it generated > maintainer scripts that called (unconditionally) programs from gconf2 to > register schemas. > > This is no longer the case. Now triggers are used by gconf, and AFAICS, > the only reason for the dependency now might be to ensure that in a partial > upgrade situation, a package that assumes gconf will be triggered is > not co-installed with an old gconf that does not support triggering. > > If that is so, it would probably be acceptable to remove the > dependencies after the next stable release. Joss, can you confirm?
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.
> (BTW, I don't think you're right about shlibs of packages that use
> libgconf2 pulling in gconf via dependencies. It seems that gconf2-common
> will be pulled in, but not gconf2 itself.)
Yes. That can be solved by moving the triggers to libgconf2-4, like what
I did for gsettings in libglib2.0-0. But that will also have to wait.
Cheers,
--
.''`. Josselin Mouette
: :' :
`. `' “If you behave this way because you are blackmailed by someone,
`- […] I will see what I can do for you.” -- Jörg Schilling
signature.asc
Description: This is a digitally signed message part
