Author: simon
Date: Tue Jan 18 22:19:55 2011
New Revision: 217562
URL: http://svn.freebsd.org/changeset/base/217562

Log:
  Decrease the libcrypto and libssl shared object version numbers from 6
  to 5. They were accidentally bumped in r215997 (on 2010-11-28) with the
  merge of OpenSSL 0.9.8p, but unfortunately this was not caught until
  now.
  
  Also add compat links for libcrypto.so.6 / libssl.so.6 (pointing to
  their .5 counterparts) in case any users have compiled any third party
  during the time stable/7 (and releng/7.4) were broken.
  
  This is deemed the last poor of bad options.  Had the number bump not
  been reverted binary packages for stable/7 would not have worked on the
  still supported 7.3 and 7.1 releases.
  
  Discussed with:       re, portmgr
  Approved by:  re (kensmith - in principle)
  Pointyhat to: simon

Modified:
  stable/7/secure/lib/libcrypto/Makefile
  stable/7/secure/lib/libssl/Makefile

Modified: stable/7/secure/lib/libcrypto/Makefile
==============================================================================
--- stable/7/secure/lib/libcrypto/Makefile      Tue Jan 18 21:57:02 2011        
(r217561)
+++ stable/7/secure/lib/libcrypto/Makefile      Tue Jan 18 22:19:55 2011        
(r217562)
@@ -6,7 +6,9 @@ SUBDIR=         engines
 .include <bsd.own.mk>
 
 LIB=           crypto
-SHLIB_MAJOR=   6
+SHLIB_MAJOR=   5
+
+SYMLINKS=      lib${LIB}.so.5 ${SHLIBDIR}/lib${LIB}.so.6
 
 NO_LINT=
 

Modified: stable/7/secure/lib/libssl/Makefile
==============================================================================
--- stable/7/secure/lib/libssl/Makefile Tue Jan 18 21:57:02 2011        
(r217561)
+++ stable/7/secure/lib/libssl/Makefile Tue Jan 18 22:19:55 2011        
(r217562)
@@ -1,7 +1,9 @@
 # $FreeBSD$
 
 LIB=           ssl
-SHLIB_MAJOR=   6
+SHLIB_MAJOR=   5
+
+SYMLINKS=      lib${LIB}.so.5 ${SHLIBDIR}/lib${LIB}.so.6
 
 NO_LINT=
 
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "[email protected]"

Reply via email to