14 Mar
2016
14 Mar
'16
11:14 p.m.
2016-03-15 0:27 GMT+03:00 Slávek Banko <slavek.banko(a)axis.cz>cz>:
On Monday 14 of March 2016 17:52:39 Fat-Zer wrote:
IMHO it doesn't...
I'm still not sure, but I suspect the "version-info" is just a
libtool-specific way to set the library version and to deal with the
dependency hell... Normal conventions like «you increase major if you
break backward compatibility, you increase minor if you break forward
compatibility and you increase revision if you break neither» seams to
me more straight-forward and got mostly the same meaning... May be
this version syntax is also a workaround for some weird platforms
nobody cares about any-more.
Afterall I don't think we are in general too careful (should we/are
we?) about such things because of very limited man-power... so I
suspect we don't even really support release mixing (do we?) and there
are no third-party applications that depends on us (except a couple in
the neighbouring thread)...
I still don't really understand what the
version-info is and what for
libtool versioning is used but I figured out how the "1.2.0" is
related to 3:0:2 : It's (current-age).(age).(revision).
Can make a sense to add to the macro tde_add_library possibility to specify
version by option VERSION_INFO - with the same behavior as is in libtool?
What do you think?