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 616313 - Add equivalent to gconftool
Add equivalent to gconftool
Status: RESOLVED FIXED
Product: glib
Classification: Platform
Component: gsettings
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Allison Karlitskaya (desrt)
gtkdev
Depends on:
Blocks:
 
 
Reported: 2010-04-20 16:33 UTC by Bastien Nocera
Modified: 2010-04-21 02:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2010-04-20 16:33:00 UTC 
So that people can debug their applications easily against GSettings.

A bare minimum would be:
- get/set on keys (including dumping whole schemas)
- monitor (to show changes as they happen)
Comment 1 Allison Karlitskaya (desrt) 2010-04-20 21:32:06 UTC 
Maybe a good idea.  The dconf command will handle this eventually, but it might be nice to have a schema-based tool as well.
Comment 2 Matthias Clasen 2010-04-21 00:58:38 UTC 
I've added a bare minimum now. Let me know what else you think would be useful.
Schema dumping is not quite possible, I think (short of using gvdb directly, which I'm not quite up to right now)

$ ./gsettings-tool --help
Usage:
  lt-gsettings-tool [OPTION...] SCHEMA KEY [VALUE]

Manipulate GSettings configuration

Help Options:
  -h, --help         Show help options

Application Options:
  -g, --get          get a key
  -s, --set          set a key
  -w, --writable     check if key is writable
  -m, --monitor      monitor key for changes
  -p, --path         path for the schema