Hi,
I was notified[1] by another developer that the SONAME of libcares is
always reported as 2.0.0 despite the latest versions having a larger API.
For example on my RHEL5 test box the c-ares version is quite old but
still the soname is reported as 2.0.0:
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.8 (Tikanga)
# rpm -qf /usr/lib64/libcares.so
c-ares-devel-1.6.0-5.el5
# objdump -p /usr/lib64/libcares.so | grep SONAME
SONAME libcares.so.2
# ls /usr/lib64/libcares.so*
/usr/lib64/libcares.so /usr/lib64/libcares.so.2 /usr/lib64/libcares.so.2.0.0
On Fedora 18 we are using pretty much the latest c-ares, but the SONAME
is still the same:
# cat /etc/redhat-release
Fedora release 18 (Spherical Cow)
# rpm -qf /usr/lib64/libcares.so
c-ares-devel-1.9.1-2.fc18.x86_64
# objdump -p /usr/lib64/libcares.so | grep SONAME
SONAME libcares.so.2
# ls /usr/lib64/libcares.so*
/usr/lib64/libcares.so /usr/lib64/libcares.so.2
/usr/lib64/libcares.so.2.0.0
Even the version in git in Makefile.am is 2.0.0
Are there any plans to bump the soname to reflect the API additions?
Thank you,
Jakub
[1] https://bugzilla.redhat.com/show_bug.cgi?id=950045
Received on 2013-04-23