<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/4.6.6">
</HEAD>
<BODY>
On Thu, 2014-01-09 at 12:10 -0200, Otavio Salvador wrote:
<BR>
<BLOCKQUOTE TYPE=CITE>
On Thu, Jan 9, 2014 at 9:16 AM, Phil Blundell <<A HREF="mailto:pb@pbcl.net">pb@pbcl.net</A>> wrote:<BR>
<BLOCKQUOTE>
Although libsoup did use to support direct usage of libproxy, it hasn't<BR>
done so for some time. Worse, if libsoup depends on libproxy then it<BR>
is impossible to build libproxy against webkit since webkit itself<BR>
depends on libsoup in some configurations. Fix this by removing the<BR>
extraneous entry from DEPENDS.<BR>
<BR>
Signed-off-by: Phil Blundell <<A HREF="mailto:pb@pbcl.net">pb@pbcl.net</A>>
</BLOCKQUOTE>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
<BR>
<BR>
</BLOCKQUOTE>
<BLOCKQUOTE TYPE=CITE>
Does it need a --disable-libproxy or so?
</BLOCKQUOTE>
<BR>
No. See the (old) NEWS:<BR>
<BR>
<BLOCKQUOTE>
<TT>Changes in libsoup from 2.33.90 to 2.33.92:</TT><BR>
<BR>
<TT> * LIBSOUP NO LONGER DEPENDS ON GCONF OR LIBPROXY.</TT><BR>
<TT> (see below).</TT><BR>
<BR>
<TT> * Updated SoupProxyResolverGNOME to be based on</TT><BR>
<TT> SoupProxyResolverDefault, but explicitly requesting the</TT><BR>
<TT> "gnome" GProxyResolver if it is available [#625898], and</TT><BR>
<TT> removed the old code that used GConf and libproxy directly.</TT><BR>
<BR>
</BLOCKQUOTE>
p.<BR>
<BR>
<BR>
</BODY>
</HTML>