Doug Barton ha scritto:
And what *I* am saying is that if there is a bug elsewhere, it should be
fixed elsewhere.
I agree with you, but "elsewhere" is tricky here: libtool is not
libassuan, but the libassuan tarball includes libtool, so you "have" to
use the external libtool to handle this issue correctly.
USE_AUTOTOOLS= libtool
USE_GNOME= ltverhack
Meanwhile, if anyone else wants to engage in idle
speculation it's going to be ignored. Discussion based on facts is
always welcome of course.
The fact is that libassuan 2.0.1 added a few interfaces, and so bumped
LT_CURRENT and LT_AGE to 1 (before they were 0):
# LT Version numbers, remember to change them just *before* a release.
# (Code changed: REVISION++)
# (Interfaces added/removed/changed: CURRENT++, REVISION=0)
# (Interfaces added: AGE++)
# (Interfaces removed/changed: AGE=0)
#
LIBASSUAN_LT_CURRENT=1
LIBASSUAN_LT_AGE=1
LIBASSUAN_LT_REVISION=0
This means that the new library is backward compatible with 2.0.0 and a
shared library bump is not needed, simplifying the port update.
--
Alex Dupre
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[email protected]"
