Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=676335
--- Comment #27 from Neal Becker ndbecker2@gmail.com 2011-10-03 18:30:41 EDT --- 1. Here is an example:
ls -l /usr/lib64/libunuran* lrwxrwxrwx. 1 root root 19 May 13 13:53 /usr/lib64/libunuran.so -> libunuran.so.15.0.0 lrwxrwxrwx. 1 root root 19 May 13 13:53 /usr/lib64/libunuran.so.15 -> libunuran.so.15.0.0 -rwxr-xr-x. 1 root root 732880 Feb 7 2011 /usr/lib64/libunuran.so.15.0.0
rpm -qf /usr/lib64/libunuran* unuran-devel-1.8.0-2.fc15.x86_64 unuran-1.8.0-2.fc15.x86_64 unuran-1.8.0-2.fc15.x86_64
As for glibc: rpm -q glibc glibc-2.14-5.x86_64 glibc-2.14-5.i686
rpm -qf /lib64/libc-2.14.so glibc-2.14-5.x86_64
Here, the name is glibc, and the version is 2.14. The rpmspec revision is 5. So no, the '1' is not part of the name. And the soname is handled by the dynamic linker, it's not part of the file name.
At least, that's my understanding.
2. If it has to be statically linked, I think that is OK, we just need to ask for some exception from the usual rules (statically linked binaries are discouraged).