After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 639801 - move from gconf to gsettings
move from gconf to gsettings
Status: RESOLVED FIXED
Product: gnome-session
Classification: Core
Component: general
unspecified
Other All
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks: 622558
 
 
Reported: 2011-01-18 00:36 UTC by Ray Strode [halfline]
Modified: 2012-06-20 10:49 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gsm, capplet: move from gconf to gsettings (24.99 KB, patch)
2011-01-18 00:36 UTC, Ray Strode [halfline]
committed Details | Review

Description Ray Strode [halfline] 2011-01-18 00:36:48 UTC
Everyone else is jumping on the gsettings train, we should too!
Comment 1 Ray Strode [halfline] 2011-01-18 00:36:49 UTC
Created attachment 178574 [details] [review]
gsm, capplet: move from gconf to gsettings

This gets us more GNOME 3 compliant.

Note we still use gconf for autostart files that require it.
Comment 2 Christian Persch 2011-01-24 18:07:41 UTC
+++ b/data/org.gnome.desktop.session.gschema.xml.in
@@ -0,0 +1,9 @@
+<schemalist gettext-domain="gnome-session-3.0">
+ <schema id="org.gnome.desktop.session" path="/desktop/gnome/session/">

Not sure about that path; I thought the recommendation was to use /org/gnome/foo/ style paths?
Comment 3 Javier Jardón (IRC: jjardon) 2011-09-29 14:11:43 UTC
Reopening as you still require gconf in your configure.ac.

Please, set the blockers bugs to completely remove the gconf dependency on this module and then we can close this bug
Comment 4 Vincent Untz 2011-09-29 14:24:33 UTC
(In reply to comment #3)
> Reopening as you still require gconf in your configure.ac.
> 
> Please, set the blockers bugs to completely remove the gconf dependency on this
> module and then we can close this bug

Depending on gconf doesn't mean we didn't move to gsettings: the reason we depend on gconf is to support autostart files that use a gconf-based condition.

If we want to get rid of this, or to use gconftool-2 for this, please open another bug -- but let's not abuse this bug for this.
Comment 5 Javier Jardón (IRC: jjardon) 2012-06-20 10:49:36 UTC
(In reply to comment #4)
> 
> Depending on gconf doesn't mean we didn't move to gsettings: the reason we
> depend on gconf is to support autostart files that use a gconf-based condition.
> 
> If we want to get rid of this, or to use gconftool-2 for this, please open
> another bug -- but let's not abuse this bug for this.

See bug #678394 :)