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 156056 - gconftool --makefile-install-rule does not scan the config-source for a writable entry
gconftool --makefile-install-rule does not scan the config-source for a writa...
Status: RESOLVED WONTFIX
Product: GConf
Classification: Deprecated
Component: gconf
unspecified
Other All
: Normal enhancement
: ---
Assigned To: GConf Maintainers
GConf Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2004-10-21 13:41 UTC by Stefan Sauer (gstreamer, gtkdoc dev)
Modified: 2018-08-17 13:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Stefan Sauer (gstreamer, gtkdoc dev) 2004-10-21 13:41:02 UTC 
gconftool-2 seems to always use the first entry of the gconf path to install new
schemas to.
When installing a package e.g. to users homedir this fails. As a work-around one
could specify the target location using --with-gconf-source.
But IMHO gconftool should try one location after the other until it finds a
writable one.
Comment 1 André Klapper 2018-08-17 13:56:01 UTC 
GConf has been deprecated since 2011.

GConf is not under active development anymore. Its codebase has been archived:
https://gitlab.gnome.org/Archive/gconf/commits/master

dconf and gsettings are its successors. See https://developer.gnome.org/gio/stable/ch34.html and https://developer.gnome.org/GSettings/ for porting info.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent + supported version of dconf/gsettings. Thanks!