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.
Well, even if I were to adopt the libwww package and Amaya was the last software using it, I would rather keep them separated to make the whole thing less of a pain to maintain, and not have to rebuild Amaya just to fix a bug in the library. Remember the old days when XFree86 was a single gigantic source package... >> 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. I surely will work towards this solution, though my experience with upstream makes me believe it's going to be a veeeeeery long process to get it accepted... > Would you maybe be interested in taking over maintainership of libwww? That's something I could consider. However, more in a "maintained end-of-life cycle" way than properly active maintainership. Will probably wait for new year to do that anyway, as I will be on holiday from this evening until the 1st. > BTW, currently the following unstable packages build-dep on libwww: > amaya liboop mapserver wmweather+ xdvik-ja xmlrpc-c I guess I will check with them to see if they have plans to move away from libwww. Thanks, Regis
