Re: Bug#858398: Proposed (lib)curl switch to openssl 1.1
On Tue, 20 Feb 2018, Steve Langasek wrote:
In fact, some of us who remember are still around ;-) The historical
context here is that curl upstream made a determination that the SONAME
should be bumped for an "ABI break" that was not an ABI break in any
traditional sense, didn't appear to break compatibility in any meaningful
way
I too am still around! I was the main curl developer upstream then and I am
still that now and I disagree with that description.
In 2006 we (the curl project) broke compatiblity with older libcurls by
removing support for several options that we previously supported, involving
what is called "third party FTP transfers". Hence, the API was made not
backwards-compatible which according to me warrants an SONAME bump.
I still believe it was the right decision we made in the curl project back
then. I leave it to you to discuss what the best decision is or was for
Debian.
(And for the record: we have not bumped the SONAME since...)
--
/ daniel.haxx.se
Reply to: