Re: Bug#318590: Bug#325643: libcurl and moc
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. dom -[ Domenico Andreoli, aka cavok --[ http://people.debian.org/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#318590: Bug#325643: libcurl and moc
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. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: Bug#318590: Bug#325643: libcurl and moc
On Fri, Sep 02, 2005 at 11:56:13AM +0200, Adeodato Simó wrote: * Domenico Andreoli [Fri, 02 Sep 2005 11:16:28 +0200]: - libcurl3-dev (OpenSSL, depends: libssl-dev) - libcurl3-openssl-dev (GnuTLS, depends: libgnutls-dev) Obvious typo/whatever here, right? On Fri, Sep 02, 2005 at 02:58:05AM -0700, Steve Langasek wrote: Your -dev package names seem to be crossed, relative to the corresponding lib packages. I think you really wanted to say - libcurl3-dev (GnuTLS, depends: libgnutls-dev) - libcurl3-openssl-dev (OpenSSL, depends: libssl-dev) ? yes - 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? thanks domenico -[ Domenico Andreoli, aka cavok --[ http://people.debian.org/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#318590: Bug#325643: libcurl and moc
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. But no one has yet answered my question: *why* are there ABI differences between the gnutls and openssl builds? -- 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
Re: Bug#318590: Bug#325643: libcurl and moc
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) But no one has yet answered my question: *why* are there ABI differences between the gnutls and openssl builds? If I've understood correctly, it is because curl expects the client program or library to -lgnutls or -lopenssl and therefore provide the SSL symbols to match the symbols which that build of the .so file is expecting. This is the point I move from suggesting things to spectating, 'cause I can't wrap my head above the reason for the above. -- --- Paul TBBle Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] No survivors? Then where do the stories come from I wonder? -- Capt. Jack Sparrow, Pirates of the Caribbean License: http://creativecommons.org/licenses/by/2.1/au/ --- pgp1SrJ1iiTdO.pgp Description: PGP signature
Re: Bug#318590: Bug#325643: libcurl and moc
On Sep 02, Paul TBBle Hampson [EMAIL PROTECTED] wrote: If I've understood correctly, it is because curl expects the client program or library to -lgnutls or -lopenssl and therefore provide the SSL symbols to match the symbols which that build of the .so file is expecting. I hope not, this would be horribly wrong. -- ciao, Marco signature.asc Description: Digital signature
