Any examples of complex gconf -> gsettings data conversion
- From: Stef Walter <stefw gnome org>
- To: "desktop-devel-list gnome org" <desktop-devel-list gnome org>
- Subject: Any examples of complex gconf -> gsettings data conversion
- Date: Sat, 28 Aug 2010 21:30:00 -0500
What's the best practice for complex gconf -> gsettings data conversion.
I know about gsettings-data-convert, but in the case of gnome-keyring we
want to combine the content of two keys.
When I tried to code this manually the following questions came up, and
I figured someone may have already figured some of this out:
* When to run migration? In main app process on startup, or is it
better in a helper binary?
* Does such an app keep a dependency on gconf?
* Keeping track of migrated data.
* How can we detect if a key already exists in gsettings in
order not to overwrite it? I don't see an g_settings_* API for this.
* I know about g_setenv ("GSETTINGS_BACKEND", ...), but how does
an app switch back to the default backend?
Cheers,
Stef
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]