On Sat, Sep 03, 2005 at 04:12:43PM +0200, Domenico Andreoli wrote: > On Fri, Sep 02, 2005 at 04:04:27AM -0700, Steve Langasek wrote: > > On Fri, Sep 02, 2005 at 12:24:18PM +0200, Domenico Andreoli wrote: > > > > > - libcurl3 (GnuTLS, soname: libcurl.so.3) > > > > So the libcurl3 in sarge and etch will have ABI incompatibilities? > > > at the release time of etch this problem will regard only > > > external software. this kind of installations will be able to use > > > libcurl3-openssl-dev package or switch to GnuTLS. > > > is this reasonable enough? > > No, definitely not. You cannot change the ABI of an existing library > > package, especially not one that's been in a stable release; you need > > to rename it instead. > so we need both libcurl3-openssl and libcurl3-gnutls until libcurl4? i > am not seeing this as a problem. If there is really a reason to regard the SSL_CTX change as an ABI change, then yes, that may be the best option. I don't know if we need to consider SSL_CTX an ABI incompatibility, though. -- 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