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 625898 - Port to GSettings
Port to GSettings
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: Misc
unspecified
Other Linux
: Normal normal
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks: 622558
 
 
Reported: 2010-08-03 00:45 UTC by Robert Ancell
Modified: 2011-03-21 17:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Comment 1 Dan Winship 2010-08-03 13:13:58 UTC 
this is slightly tricky in that we depend on libproxy seeing the same proxy settings as we do, so we don't want to look at the gsettings version unless either (a) the control-center is also updating the gconf keys to match gsettings, or (b) libproxy has been updated to look in gsettings as well
Comment 2 Murray Cumming 2010-11-07 13:41:29 UTC 
Can't you just assume that gconf is not used by any of these, at least in newer versions of libsoup?

Or could we at least have a configure setting, such as --disable-gconf configure option, to remove the build dependency from the GNOME 3 build, for instance when building in jhbuild? (libsoup is currently an external dependency of GNOME 3.0).
Comment 3 Andreas Henriksson 2010-11-28 22:44:02 UTC 
For the record, here's the link to the discussion about porting libproxy to gsettings:
http://code.google.com/p/libproxy/issues/detail?id=131
Comment 4 Dan Winship 2011-03-11 01:40:10 UTC 
bug 644211 adds a GSettings-based GProxyResolver to glib-networking. Bug 642928 adds a GProxyResolver-based SoupProxyResolver to libsoup. Those two combined fix this bug.
Comment 5 Dan Winship 2011-03-21 17:31:41 UTC 
fixed in git. libsoup no longer depends on gconf (or libproxy)