#1 No SONAME for libJudy
When Judy builds, you end up with 'libJudy.a' and
'libJudy.so' (on
Linux, anyhow). The problem with this is that there's
no version
information in the library name, so you can't tell what
version of
the library you're linking against, or force yourself
to only link against
a known-good version of the library.
There's a good discussion of this in the libtool
manual, at
http://www.gnu.org/software/libtool/manual.html#Libtool%20versioning
I'm currently attempting to package judy for Debian
right now, and
I'm provisionally assigning the current release a
SONAME of
'0.0.1', thus giving 'libJudy.so.0.0.1', and
'libJudy.so.0'. I hope
you guys were planning on doing something like this
anyway, so
consider this your first official Judy packaging bug. :)
-=Eric Schwartz
Logged In: YES
user_id=558029
Eric:
Thank you for your submittal. I am new to the open source
community. I feel kind of green even using this small box
to reply to this bug. However, I will read the 58 page document
you have suggested and update Judy when I get the rest of it
up in the CVS tree.
Doug Baskins
doug@sourcejudy.com
Logged In: YES
user_id=558029
I can identify with your frustration -- I would be pissed.
I /we are presently
working on the problem. We put Judy in open source very
quickly and did a
very poor job of it. It had to be done quickly or possibly
loose the opportunity.
I/we are working on using the autoconf, automake, and
libtool to make Judy
portable across a broad range of platforms.
Logged In: YES
user_id=313104
Thank you Doug, you're a good author and a responsive one at
that.
I'm, too, giving it a SONAME of 'libJudy.so.0' for the
Altlinux distribution.
When you "autoconfiscate" Judy and make any ABI-incompatible
changes, be sure to bump the soname number to 1, in order to
play safe with your package vendors, now counting at two :-)
Logged In: YES
user_id=558029
Eric:
So take a look at 0.1.7 in <http://judy.sourceforge.net/downloads> and
give me a patch on what to do.
Thanks,
Doug