SoupProxyResolverGNOME: improve behavior with more-recent libproxy
authorDan Winship <danw@gnome.org>
Mon, 7 Jun 2010 12:57:52 +0000 (14:57 +0200)
committerDan Winship <danw@gnome.org>
Tue, 8 Jun 2010 15:45:45 +0000 (11:45 -0400)
commit25bfd5cbcfb93b94efc7c0f6f0d4bbfa51244e42
tree02ffa50d147ff4690468086d3d893416a1ffd1b4
parent34ae2a292b69321078c5e7d922a39f75e8538d3a
SoupProxyResolverGNOME: improve behavior with more-recent libproxy

SoupProxyResolverGNOME had a nasty workaround for the fact that
libproxy 0.2 would crash inside GConf if called from a thread other
than the main one. Unfortunately, the workaround involves leaking
proxy settings into the environment, which is particularly bad since
gnome-panel uses libsoup (via libgweather via intlclock) and so the
environment can become polluted for everything started from the panel.

In libproxy 0.3 and later, the workaround is no longer necessary, so
remove it if libproxy is new enough.

https://bugzilla.gnome.org/show_bug.cgi?id=603285
configure.ac
libsoup/soup-proxy-resolver-gnome.c