Hi Steve, On Fri, Feb 25, 2005 at 10:38:52AM -0800, Steve Langasek wrote: > > Upstream SONAME has changed to libldap2.2. > > grabbing the package from http://pkg-openldap.alioth.debian.org/openldap2.2/ > (thanks, Stephen):
?? What's Stephen got to do with it? > $ dpkg -x libldap2.2_2.2.23-0.pre2_i386.deb /tmp/ldap-unpack && objdump -p > /tmp/ldap-unpack/usr/lib/libldap-2.2.so.7.0.16 | grep SONAME > SONAME libldap-2.2.so.7 > > So no, libldap2.2 is *not* what the upstream SONAME was changed to. Okay, so it was changed to libldap-2.2.so.7. Or what? I'll never grok this SONAME stuff. From the output above I'd say that the SONAME is "libldap-2.2.so.7". Reading random documentation about it (for example at http://lists.debian.org/debian-mentors/2002/03/msg00125.html) the SONAME is just "7" in this case. So depending on what the soname is the package is either libldap7 (going from section 8.1 of Debian policy) or libldap-2.2-7 which I find hard to grok (but which does not matter as it should normally get installed automatically). The point I tried to make though was that the upstream SONAME changed and libldap from OpenLDAP 2.2 does not class with libldap from OpenLDAP 2.1. Apart from that I spent the last two days solely on working on OpenLDAP packaging and the only feedfack is that I misrepresented the SONAME. And I still got no idea what your point is. If you want the library package to be libldap-2.2-7 that's fine with me. I can rename that package if you want me to. I like libldap2.2 better as it is in line with libldap2 (which I did not invent) but I don't really care. Greetings Torsten
signature.asc
Description: Digital signature
