Bug#509932: shlibs format only addresses one versioning structure
Kurt Roeckx <kurt@roeckx.be> writes:
> On Sun, Feb 01, 2009 at 11:21:55AM -0800, Russ Allbery wrote:
>> Yes, quite a few. All of the libdb<version> packages, for instance.
>>
>> windlord:~> dpkg -L libdb4.6 | grep /usr/lib/
>> /usr/lib/libdb-4.6.so
>> windlord:~> readelf -d /usr/lib/libdb-4.6.so | grep SONAME
>> 0x0000000e (SONAME) Library soname: [libdb-4.6.so]
> Is there any reason they're not using libdb.so.4.6 as soname?
> It's of course to late to change it for current versions of the
> library, but I do have to wonder.
I'm not sure, but there are other packages that do this. Just on my local
system:
0x0000000e (SONAME) Library soname: [liba52-0.7.4.so]
0x0000000e (SONAME) Library soname: [libbfd-2.20.1-system.20100303.so]
0x0000000e (SONAME) Library soname: [libdb-4.5.so]
0x0000000e (SONAME) Library soname: [libdb-4.6.so]
0x0000000e (SONAME) Library soname: [libdb-4.7.so]
0x0000000e (SONAME) Library soname: [libdb-4.8.so]
0x0000000e (SONAME) Library soname: [libdb-4.8.so]
0x0000000e (SONAME) Library soname: [libdb_java-4.7.so]
0x0000000e (SONAME) Library soname: [libgettextlib-0.17.so]
0x0000000e (SONAME) Library soname: [libgettextsrc-0.17.so]
0x0000000e (SONAME) Library soname: [libopcodes-2.20.1-system.20100303.so]
0x0000000e (SONAME) Library soname: [libpulsecommon-0.9.21.so]
0x0000000e (SONAME) Library soname: [libxerces-c-3.0.so]
0x0000000e (SONAME) Library soname: [libxerces-c-3.1.so]
It's also the SONAME versioning implemented by libtool if you use the
-release flag, which is intended for packages whose ABI changes with each
major release of the package. libtool recommends against it for public
libraries, but people seem to use it anyway.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: