Re: TODO #1: GNOME 1.x and 2.0 interoperability

[Martin Baulig <martin home-of-linux org>]

Jonathan Blandford <jrb redhat com> writes:

> Huh?  Why is GConf optional???  Surely most applications will want to
> use it?  And what is bonobo config?

At the moment, it's optional for the GNOME 2 build since none of the core
libraries need it.

You can compile bonobo-config either with or without GConf, but this only
affects whether the "gconf:" moniker is built or not.

However, this has no side effects whatsoever, not even from a binary packaging
perspective - if you compile bonobo-config with GConf, you'll get exactly the
same binaries, it'll just install two more files (a .so and a .oaf file).

So you can make binary packages of GNOME 2 which is compiled without GConf,
but this doesn't mean that you cannot use GConf. You can even use bonobo-config
with the GConf backend; all you need to do is to compile and install the "gconf:"
moniker.

Ideally, this moniker should be in gconf anyways, as this'd allow us to make
binary packages of GNOME 2 which do not depend on gconf, but which can still
use it.

-- 
Martin Baulig
martin gnome org (private)
baulig suse de (work)