On Sun, Sep 11, 2005 at 12:24:13PM +0200, Daniel Stenberg wrote: > I just want to (once again) point out that the people on the debian-devel > list are wrong:
> http://curl.haxx.se/legal/distro-dilemma.html > There are more to this problem than a single libcurl option not used by any > debian-provided package. The only explanation I see at that URL is libcurl has different ABI when built with different SSL/TLS libraries due to two reasons: 1. No one has worked on fixing this. The mutex/lock callbacks should be set with a generic libcurl function that should use the proper underlying functions. 2. The CURLOPT_SSL_CTX_FUNCTION option is not possible to "emulate" on GnuTLS but simply requires OpenSSL. We've already identified that the CURLOPT_SSL_CTX_FUNCTION option is of negligible importance to Debian, and does not (from my POV) appear to warrant a separate soname. The description of the other issue ("mutex/lock callbacks") doesn't give me enough information as an outsider to understand why this has an effect on the ABI. Can you elaborate? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
