Hi,
Thomas Lord <lord at emf.net> writes:
> AndrevanTonder wrote:
>> I'm not sure I understand the issue you mention. With my simple suggestion, a
>> client import of 6.2 will match the bug-fixed 6.2.1, and import the latter, as
>> desired.
>
> That concept is messed up.
>
> It assumes that the question "should 6.2.1 be used instead
> of 6.2?" has the same answer for all applications that
> happened to allow both version numbers in their imports.
I think Libtool's view of library versioning is worth considering:
So, libtool library versions are described by three integers:
current
The most recent interface number that this library implements.
revision
The implementation number of the current interface.
age
The difference between the newest and oldest interfaces that this
library implements. In other words, the library implements all the
interface numbers in the range from number current - age to
current.
If two libraries have identical CURRENT and AGE numbers, then the
dynamic linker chooses the library with the greater revision number.
http://www.gnu.org/software/libtool/manual.html#Libtool-versioning
Imports and exports could be structured around those three numbers
rather than generic "version numbers" with unspecified semantics.
That said, it may be a bit too much to specify...
Thanks,
Ludovic.
Received on Thu Jun 21 2007 - 04:10:50 UTC