Mon 24 Nov 2008 12:56:07 PM UTC, comment #2:
This is also related to the bug #24854.
Incrementing SO version with CERTI version (the 1-1 relation) is an easy way to avoid library compatibility problems: everything that was shipped together linkes together and nothing else.
Other relations may be more user-convenient, but requires CERTI developers to track and test the API compatibility.
1) The libRTI-NG and libFedTime
Here the 1-1 relation is obviously wrong, you're right. The API does not change. We may even leave 1.0.0 here, because the libRTI versioning is implemented through changing the name (librti13, librti1516).
2) The libHLA
It is a standalone library, so may have own numbering. On the other hand, tracking down the API changes in a library like libHLA may be very problematic.
I'm not sure here, having 1-1 is easier for CERTI development and not so inconvenient for the developpers. It just requires a single rebuild.
3) The libCERTI
I belive that libCERTI of version X.Y should be tightly linked to RTIA/RTIG of this version, so libCERTI should have the same SO version as CERTI. It's an internal library. Rebuild is not required when libCERTI version changes.
Summary:
libHLA, libFedTime : fixed 1.0.0 (current solution)
libCERTI: CERTI version (solution from my previous patch)
libHLA: CERTI version (because it's easier for me, many development libraries does this), but fixed 1.0.0 is also fine
What do you think?
|