On Fri, 2009-10-16 at 07:35 -0700, Sandy Armstrong wrote:
> On Fri, Oct 16, 2009 at 7:10 AM, Ryan Lortie <de...@desrt.ca> wrote:
> > On Wed, 2009-10-14 at 14:00 +0200, Rodrigo Moya wrote:
> >> if dconf listens to changes in gconf, 3rd party apps would just need to
> >> link to glib/GSettings instead of libgconf, and their migration would be
> >> done automatically, right?
> >
> > dconf won't be made to listen to GConf. One alternative, though, is
> > that a GSettings backend could be written that uses GConf (and its
> > existing database) instead of dconf. This would allow applications to
> > use the new API to access their existing settings in the existing
> > database.
> >
> > dconf could be brought in later.
>
> That doesn't fix anything; it just delays an identical migration.
Why not letting existing installations continue using the GConf backend,
and let only new installs use dconf ?
Then you can provide a migration script or wizard that people can run if
they want, but by default you stay in a very compatible mode.
Xav
_______________________________________________
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
