GNOME Bugzilla – Bug 662759
Port to GSettings
Last modified: 2021-06-02 11:42:16 UTC
Migrating from GConf to GSettings is an official GNOME goal now.
Depends on gsettingslist.
I started working on this.
For a starter, this is my first blunt attempt on converting the XML and adjusting the autofoo c***.
This likely has errors.
More to follow possibly soon.
Created attachment 235127 [details] [review]
autofoo stuff and XML conversion
Any progress on this? I feel that this is the last GNOME component using gconf
No progress. You can however simply configure using --with-platform=gtk-only to avoid the gconf dependency. (Stored gconf settings won't be migrated, however.)
Also, aisleriot is not a Gnome component, it's in gnome-world not core/apps/desktop.
Created attachment 326584 [details] [review]
Here is a patch that use the GSettings mechanism. No need to differentiate the environment and GSettings is a freedesktop.org component
It'll be a bit before I can review this.
There's also been a previous, unfinished, attempt, on the wip/redesign branch, which has other stuff that'll still be needed so I'm wary of introducing conflicts...
Christian, what all does --with-platform=gtk-only do?
Are there any other side effects we should know about?
There should be no other effects apart from making aisleriot use key files in ~/.config instead of gconf. (There's no settings migration from gconf, of course.)
Thanks, I've switched Ubuntu's aisleriot to --with-platform=gtk-only. It was the last thing keeping gconf in the default Ubuntu (Unity) and Ubuntu GNOME installs.
Debian stretch is getting gconf out of the default GNOME install by no longer installing aisleriot.
-- GitLab Migration Automatic Message --
This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/aisleriot/-/issues/170.