krb5 commit: Install shared libraries as executable

https://github.com/krb5/krb5/commit/1bc5f76d2e7013b8771e3bd9960c82642ba0b467
commit 1bc5f76d2e7013b8771e3bd9960c82642ba0b467
Author: Robbie Harwood <[email protected]>
Date:   Tue Aug 23 16:45:26 2016 -0400

    Install shared libraries as executable
    
    RPM expects this behavior, and systems with contrary policies (like
    Debian) address permissions at the packaging layer.  Most other build
    systems appear to install shared libraries as executable.
    
    [[email protected]: edited commit message]
    
    ticket: 8965 (new)

 src/config/shlib.conf |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/src/config/shlib.conf b/src/config/shlib.conf
index 3e4af6c..75b7cc3 100644
--- a/src/config/shlib.conf
+++ b/src/config/shlib.conf
@@ -22,8 +22,10 @@ SHLIBVEXT=.so.v-nobuild
 SHLIBSEXT=.so.s-nobuild
 # Most systems support profiled libraries.
 PFLIBEXT=_p.a
-# Most systems install shared libs as mode 644, etc. while hpux wants 755
-INSTALL_SHLIB='$(INSTALL_DATA)'
+# Install libraries executable.  Some systems (e.g., RPM-based ones) require
+# this for package dependency generation, while others are ambivalent or will
+# strip it during packaging.
+INSTALL_SHLIB='$(INSTALL)'
 # Most systems use the same objects for shared libraries and dynamically
 # loadable objects.
 DYNOBJEXT='$(SHLIBEXT)'
@@ -118,7 +120,6 @@ alpha*-dec-osf*)
 # -O +dpv should display any routines eliminated as unused, but -b
 #	  apparently turns that off
 *-*-hpux*)
-	INSTALL_SHLIB='$(INSTALL)'
 	case $host_cpu in
 	hppa*)
 		SHLIBEXT=.sl