On Wed, Oct 06, 2010 at 06:30:41AM +0200, Emilio Pozuelo Monfort wrote: > On 23/09/10 23:45, Josselin Mouette wrote: > > Le jeudi 23 septembre 2010 à 19:55 +0200, Emilio Pozuelo Monfort a > > écrit : > >> That's not true. libproxy can autodetect the proxy configuration from > >> several > >> places, libmozjs being one of them. But if you don't have it, it can still > >> autodetect it from GConf (for GNOME), some KDE mechanism (I'm not a KDE > >> guy!), > >> your environment, a configuration file... so we don't force anything to be > >> installed, because you most likely have installed something so that > >> libproxy can > >> autodetect the proxy settings. > > > > libmozjs is necessary to parse JavaScript in proxy.pac files. > > > > It would be really interesting to build again libproxy with > > Webkit/JavaScriptCore support. The circular dependency loop makes it > > hard, but it avoids this situation. > > We could enable it again, I doubt there will be a soname bump in any of the 3 > libraries in Squeeze. > > RT: I disabled webkit support in libproxy to break a dependency loop (libproxy > -> webkit -> libsoup -> libproxy) because of a transition. Would it be > acceptable if I enabled it back for Squeeze?
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). > Gustavo, I guess there are no plans of splitting JSC into its own tarball > upstream? No. Mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
