Le jeudi 30 juin 2005 à 23:50 +0200, Bill Allombert a écrit : > Package: libgnomevfs2-0 > Version: 2.10.1-5 > Severity: important > > Hello GNOME maintainers, > > There is a circular dependency between libgnomevfs2-common and > libgnomevfs2-0. > > Circular dependencies are known to cause issues during upgrade > between stable release.
This one is even more complicated than GConf. Here are the contents of libgnomevfs2-common: * modules configuration: can stay in this package; * example binaries: can probably be moved to a separate libgnomevfs2-bin package; * /usr/lib/gnome-vfs-2.0/modules/: this directory is already versioned and can probably be moved as is to libgnomevfs2-0. It's probably still possible, though, that upstream changes the SONAME without changing the modules interface. The modules would thus stay in the same directory. Moving this to libgnomevfs2-0 is thus risky. * /usr/lib/gnome-vfs2/gnome-vfs-daemon: can be moved to /usr/lib/gnome-vfs-2.0, with the same caveats; * /usr/lib/bonobo/servers/: can stay in this package; * documentation: can (should) be moved away; * schemas, l10n, default applications: can stay in this package; * /usr/lib/bonobo/monikers/libmoniker_gnome_vfs_std.so: this file is impossible to move, as the directory depends on libbonobo. We'd have to check whether it is possible to rename it. However I don't feel like it _at all_. While I'd be tempted to make the move for gconf2, as applications shouldn't be affected, I'm currently not convinced the benefits of doing it for libgnomevfs2 outweigh the risks. Regards, -- .''`. Josselin Mouette /\./\ : :' : [EMAIL PROTECTED] `. `' [EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
signature.asc
Description: This is a digitally signed message part
