Bug#316437: circular dependency between libgnomevfs2-common and libgnomevfs2-0

[Josselin Mouette]

--=-oJlBbdh3m8/dFPG75eOZ
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

Le jeudi 30 juin 2005 =E0 23:50 +0200, Bill Allombert a =E9crit :
> Package: libgnomevfs2-0
> Version: 2.10.1-5
> Severity: important
>=20
> Hello GNOME maintainers,
>=20
> There is a circular dependency between libgnomevfs2-common and
> libgnomevfs2-0.=20
>=20
> Circular dependencies are known to cause issues during upgrade
> between stable release.=20

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,
--=20
 .''`.           Josselin Mouette        /\./\
: :' :           josselin.mouette@ens-lyon.org
`. `'                        joss@debian.org
  `-  Debian GNU/Linux -- The power of freedom

--=-oJlBbdh3m8/dFPG75eOZ
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBCxHQ1rSla4ddfhTMRArtfAKCl7DW6weoAH4uaLg+R6ttSofiw/gCePqO+
kP5TEYym9B/XEpw9kMN8uJQ=
=A8sp
-----END PGP SIGNATURE-----

--=-oJlBbdh3m8/dFPG75eOZ--