Bug#597864: libproxy0 not functional without libmozjs2d

[Josselin Mouette]

Le mardi 19 octobre 2010 à 20:13 +0100, Adam D. Barratt a écrit : 
> On Wed, 2010-10-06 at 09:29 +0200, Josselin Mouette wrote:
> > Le mercredi 06 octobre 2010 à 08:12 +0200, Mike Hommey a écrit :
> > > Does that mean libproxy will depend (as in Depends control field) on
> > > webkit ? That's going to be a problem later, because iceweasel 4.0 may use
> > > libproxy (I enabled it, but I'm not entirely sure I'll keep it that way).
> > 
> > No. It doesn’t depend on libmozjs either, it uses whatever is available
> > on the system if it has been built against it.
> 
> 0.3.1-2 does have a Recommends on libwebkit | libmozjs, however.

Yes, it’s intentional. Do you think it is a problem?

The primary issue I see with this change it that it doesn’t handle
binNMUs correctly.

Note that I intend to work with libsoup upstreams to get rid of libproxy
for squeeze+1. I’d recommend against iceweasel using libproxy directly.

Cheers,
-- 
 .''`.      Josselin Mouette
: :' :
`. `'  “If you behave this way because you are blackmailed by someone,
  `-    […] I will see what I can do for you.”  -- Jörg Schilling
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20101019/5e30966d/attachment.pgp>