From 6a919b44f745c1d764b6b0593b2a60bd8e342c67 Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Sun, 29 Mar 2015 09:42:58 +0200 Subject: Have a shared library version thats reasonable with our version scheme The FAQ says this: After the release of OpenSSL 1.0.0 the versioning scheme changed. Letter releases (e.g. 1.0.1a) can only contain bug and security fixes and no new features. Minor releases change the last number (e.g. 1.0.2) and can contain new features that retain binary compatibility. Changes to the middle number are considered major releases and neither source nor binary compatibility is guaranteed. With such a scheme (and with the thinking that it's nice if the shared library version stays on track with the OpenSSL version), it's rather futile to keep the minor release number in the shared library version. The deed already done with OpenSSL 1.0.x can't be changed, but with 1.x.y, x=1 and on, 1.x as shared library version is sufficient. Reviewed-by: Kurt Roeckx --- crypto/opensslv.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'crypto/opensslv.h') diff --git a/crypto/opensslv.h b/crypto/opensslv.h index b86665ddca..97c27e79ea 100644 --- a/crypto/opensslv.h +++ b/crypto/opensslv.h @@ -88,7 +88,7 @@ extern "C" { * should only keep the versions that are binary compatible with the current. */ # define SHLIB_VERSION_HISTORY "" -# define SHLIB_VERSION_NUMBER "1.1.0" +# define SHLIB_VERSION_NUMBER "1.1" #ifdef __cplusplus -- cgit v1.2.3