ABI: 2.0.x, 2.1.x #1997
-
|
Are the 2.0.x, 2.1.x releases intended to be ABI compatible? It would be nice if the VERSION and SOVERSION schemes were documented to save people from detailed commit reviews. Also, there's an ABI check feature that seems to exist in |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
SOVERSION follows the semver versioning scheme as one would expect. However, we do have a separate API version for plugins that changes sometimes and includes NBC changes but it is stored in every plugin so obsolete ones will refused to be loaded. Meaning you should have no unexpected problems when updating libyang when keeping the same major SO version, they are API/ABI compatible. That |
Beta Was this translation helpful? Give feedback.
SOVERSION follows the semver versioning scheme as one would expect. However, we do have a separate API version for plugins that changes sometimes and includes NBC changes but it is stored in every plugin so obsolete ones will refused to be loaded. Meaning you should have no unexpected problems when updating libyang when keeping the same major SO version, they are API/ABI compatible.
That
ABICheckmodule is not documented because it is used mostly internally for checking that we do not accidentally make a NBC change but is also used to generate compatibility reports.