On Sat, December 15, 2007 11:42, Richard Atterer wrote: > On Fri, Dec 14, 2007 at 05:38:12PM -0000, Regis Boudin wrote: >> Amaya build-depends on libwww and seriously relies on it. Removing it >> will put me in a quite uncomfortable situation. I would like to avoid >> following upstream who use a statically built and linked version of the >> library if I can. > > Hmm, OK. Using a statically linked version would have been my first > suggestion. > >> I could try to push them towards libcurl, though I'm afraid they won't >> react well... > > Having tried to create a program using both libwww and libcurl, I can say > that libcurl is _much_ better in every aspect. These days, libcurl can > even > do HTTP pipelining, which was only supported by libwww for a long time.
OK, the good news is, upstream reacted very positively to my suggestion to switch to libcurl. One thing I'm not sure about yet is how to handle WebDAV with it. Not much of a problem for me at the moment anyway, considering the feature is disabled in both libwww and Amaya... > Would you maybe be interested in taking over maintainership of libwww? > BTW, currently the following unstable packages build-dep on libwww: > amaya liboop mapserver wmweather+ xdvik-ja xmlrpc-c mapserver is actually a false positive, they switched to libcurl ages ago, bug filed. Seems to be the case with xdvik-ja too. Which only leaves : amaya liboop (reverse b-dep are lsh-utils, and ruli) wmweather+ xmlrpc-c (reverse b-dep are libapache2-mod-xmlrpc2, openser, and rtorrent) As I wrote previously, I will be happy to take over maintainership until it can be actually removed. How do you want me to handle this ? Simply make an upload setting myself as new maintainer ? Regis
