On Sun, Nov 20, 2016 at 07:40:22PM +0400, Stepan Golosunov wrote: > If SONAME change is needed it is needed when linking libcurl with > libssl1.0.2 too. (But when linking libcurl with libssl1.0.2 more > applications are affected due to the need of explicit initialization.)
Upstream documentation suggests that this is not true: "Minor releases that change the last digit, e.g. 1.0.1 vs. 1.0.2, can and are likely to contain new features, but in a way that does not break binary compatibility. This means that an application compiled and dynamically linked with 1.0.0 does not need to be recompiled when the shared library is updated to 1.0.2." (https://www.openssl.org/policies/releasestrat.html) But of course, in practice, there may have been unintended ABI changes - so yes, may be a SONAME change is nessary for 1.0.2 as well. I just don't know. Still, for 1.1 the SONAME change is definitely necessary. Jan
