suboptimal library versioning of libacl and libattr

[Kamil Dudka]

The library versioning scheme used for libacl and libattr causes problems 
while upgrading the libraries with rpm package manager.  The new libraries
are installed as:

    /lib64/libacl.so.1.1.230
    /lib64/libattr.so.1.1.250

... which is seen (by ldconfig) as older than originally installed libraries:

    /lib64/libacl.so.1.1.2253
    /lib64/libattr.so.1.1.2448

Consequently, if ldconfig is invoked after the new version of the library
is installed but before the old version of the library is removed, it 
incorrectly overwrites the already installed symlinks:

    /lib64/libacl.so.1
    /lib64/libattr.so.1

... such that they point to the old libraries again.  Then removing old 
versions of the libraries introduces dangling symlinks and all attempts
to load the libraries fail until ldconfig is invoked again.

Originally reported at:

    https://bugzilla.redhat.com/1938459#c9

Kamil