On Sun, Sep 04, 2005 at 07:47:15PM +1000, Paul TBBle Hampson wrote: > > It may be worthwhile to simply survey all the curl-using packages in > > sarge, though, and find out if there is a non-zero number of them that > > need SSL_CTX_FUNCTION. If *not*, then I don't think there's much sense > > in going through a multi-stage transition: just switch libcurl3 directly > > to gnutls, and add libcurl3-openssl which provides libcurl-openssl.so.3? > BINDINGS: > * curl itself only uses it in > - lib/url.c (implementation) > - tests/libtest/lib509.c (test of functionality) > - docs/examples/curlx.c (demonstration of usage) > * libwww-curl-perl doesn't use it itself, but exports it for perl > users to use. (But it doesn't show any rdepends here...) > * pycurl doesn't support it. > * tclcurl documents it as not supported Right, so I think the fact that libwww-curl-perl exports it shouldn't influence the decision; we still have nothing in Debian that *uses* it, libwww-curl-perl is just passing it through. > So unless I'm missing something, this is a complete non-issue... You > could upload a libcurl3 built against gnuTLS, and see what breaks. ^_^ FWIW, I agree. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. vorlon@debian.org http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature