cvs commit: ports/security/dirmngr Makefile ports/security/gnupg
Makefile ports/security/gpa Makefile ports/security/gpgme Makefile
ports/security/libassuan
Makefile distinfo pkg-descr ports/security/opensc Makefile
Alex Dupre
ale at FreeBSD.org
Fri Dec 24 07:08:40 UTC 2010
Doug Barton ha scritto:
> I am willing to be educated here, so help me out. What is "this issue,"
> what is libassuan not doing correctly, and what is the different thing
> that those 2 knobs are going to do that is correct?
To begin with, it's not libassuan issue, but a FreeBSD specific
libtool-included-in-libassuan issue.
> It sounds to me like what you're saying here is that you disagree with
> the vendor's choice to bump the library version, and you would prefer
> that in my port I override their decision.
No, it's not so. The vendor didn't want to bump shared library version,
in fact he bumped *both* LT_CURRENT and LT_AGE. If the new API was
incompatible he'd bumped only LT_CURRENT. Shared library version is
calculated by libtool (on Linux) as LT_CURRENT - LT_AGE, so from 2.0.0
and 2.0.1 it remained ".0". The "bugged" included libtool calculates (on
FreeBSD) the library version only as LT_CURRENT, so it erroneously
changed it to ".1". What the above two Makefile lines do is fix such
"issue", by using the external libtool and correcting the calculus.
--
Alex Dupre
More information about the cvs-ports
mailing list