Bug#440436: Amaya will be hurt
On Wed, Jan 02, 2008 at 03:52:17PM -, Regis Boudin wrote: On Sat, December 15, 2007 11:42, Richard Atterer wrote: 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. That's great! TBH, I'm not too surprised, libwww _is_ difficult to get to work at times. 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... WebDAV support is raised on the libcurl mailing list from time to time. Curl doesn't directly support WebDAV, but you can generate quite arbitrary HTTP-like requests with it, including overwriting the request method with e.g. MKCOL rather than GET/POST. So it should be possible to get it to work. Alternatively, WebDAV support could be added to curl. Having hacked libcurl on several occasions, I can say that its code is quite beautiful and fun to work with, in contrast to libwww... Well, or look at libneon. 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 ? Yes, feel free to take over maintainership this way! (Close this bug with the upload if you do plan to take it over permanently, and not only until Amaya has moved to libcurl.) BTW, if you keep the package in the archive, consider getting rid of the non-SSL versions. I introduced them because of possible license incompatibilities between any GPL packages and OpenSSL, but last time I checked (=a long time ago!;-), there weren't actually any such problems with the current depends in the Debian archive. Cheers, Richard -- __ _ |_) /| Richard Atterer | \/¯| http://atterer.net ¯ '` ¯ signature.asc Description: Digital signature
Bug#440436: Amaya will be hurt
On Thu, 2008-01-03 at 21:49 +0100, Richard Atterer wrote: OK, the good news is, upstream reacted very positively to my suggestion to switch to libcurl. That's great! TBH, I'm not too surprised, libwww _is_ difficult to get to work at times. I was more referring to issues I have with amaya upstream to get some patches included. There a couple I've had for over a year. 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... WebDAV support is raised on the libcurl mailing list from time to time. Curl doesn't directly support WebDAV, but you can generate quite arbitrary HTTP-like requests with it, including overwriting the request method with e.g. MKCOL rather than GET/POST. So it should be possible to get it to work. Alternatively, WebDAV support could be added to curl. Having hacked libcurl on several occasions, I can say that its code is quite beautiful and fun to work with, in contrast to libwww... Well, or look at libneon. Sounds good to me :) 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 ? Yes, feel free to take over maintainership this way! (Close this bug with the upload if you do plan to take it over permanently, and not only until Amaya has moved to libcurl.) Actually, liboop has had the libwww bit disabled for years, and xmlrpc-c already has a libcurl connector. I already filed bugs for the 4 easy ones, which only leaves amaya and wmweather+. I sincerely hope to get rid of libwww at some point. BTW, if you keep the package in the archive, consider getting rid of the non-SSL versions. I introduced them because of possible license incompatibilities between any GPL packages and OpenSSL, but last time I checked (=a long time ago!;-), there weren't actually any such problems with the current depends in the Debian archive. I'm not sure I want to do that much work on this package ;) Regis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#440436: Amaya will be hurt
On Sat, December 15, 2007 11:42, Richard Atterer wrote: On Fri, Dec 14, 2007 at 05:38:12PM -, 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
Bug#440436: Amaya will be hurt
On Sat, December 15, 2007 11:42, Richard Atterer wrote: On Fri, Dec 14, 2007 at 05:38:12PM -, 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 veery 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
Bug#440436: Amaya will be hurt
On Fri, Dec 14, 2007 at 05:38:12PM -, 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. 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 Cheers, Richard -- __ _ |_) /| Richard Atterer | \/¯| http://atterer.net ¯ '` ¯
Bug#440436: Amaya will be hurt
Hi Richard, 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. I could try to push them towards libcurl, though I'm afraid they won't react well... Regis
