Hi,
as I have noticed a few rants in bug reports about packages depending on
gconf2 while their GConf related functionality is optional, I have tried
to improve the situation a bit.
As of gconf2 2.20.1-1, the package now registers schemas and defaults
that have not yet been registered before. Which means you should be able
to safely drop the dependency on gconf2 *if the functionality is
optional*. This only concerns a small number of packages and involves
dropping ${misc:Depends}, but I thought some of you should be
interested.
Cheers,
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`- our own. Resistance is futile.
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=