Le jeudi 30 juin 2005 à 21:01 +0200, Bill Allombert a écrit : > Package: libgconf2-4 > Version: 2.10.0-2 > Severity: important > > Hello Takuo, > > libgconf2-4 has a circular dependency with gconf2. > This cause problems during upgrade between stable releases. > > We are discussing circular dependencies on debian-devel and > Josselin Mouette asked me to report this bug as a reference > for the discussion.
Alright. This case is similar to fontconfig, but much, much trickier.
The gconf2 package includes:
* the gconfd-2 daemon,
* the backends for the daemon,
* localization data,
* documentation,
* configuration,
* gconftool-2.
Localization data and configuration are not a problem. They can be put
in a gconf2-common package (modulo the conffile-move issues).
Documentation can be split out or put in libgconf2-dev.
The gconftool-2 binary has to stay in the gconf2 package for a clean
upgrade path from sarge, as many packages need it at postinst/prerm
time. There is a debhelper script named dh_gconf but not all packages
use it. It generates ${misc:Depends} but not all packages use it. So
before doing anything, this requires a mass bug-filing against packages
shipping .schema files and not depending upon gconf2.
We could move gconfd-2 and the backends to /usr/lib/libgconf2-4/, and
let them in libgconf2-4. However we should be *very* careful about doing
that. It means not forgetting any path in the library, and hoping it's
not used anywhere else (which would be bad(tm), but you never know).
In short, it's possible but very complicated. Maybe we can do it
together with the defaults-to-/var migration. I'm still unsure it's
worth the deal.
Regards,
--
.''`. Josselin Mouette /\./\
: :' : [EMAIL PROTECTED]
`. `' [EMAIL PROTECTED]
`- Debian GNU/Linux -- The power of freedom
signature.asc
Description: This is a digitally signed message part
