Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

soname policy #103

Closed
sergey-239 opened this issue Oct 16, 2022 · 1 comment
Closed

soname policy #103

sergey-239 opened this issue Oct 16, 2022 · 1 comment
Labels

Comments

@sergey-239
Copy link
Contributor

Joseph,
I remember that you have no versioning policy in general.
However, in the review response [0] reviewer points that it probably good to have your decision on soname and its versioning. I replied:

As 1) Joseph adds the functionality on as needed basis, 2) there
are obvious bugfixes, 3) camotics builds properly with up-to-date version of cbang
and 4) cbang exports c++ classes, I decided to use `version.subversion` as an so version,
leaving `.revision` for bug fixes in cbang. The leading zero in `libcbang0` is from 
upstream, I suspect that it is somehow related to debian packaging/naming, so I 
leaved this as is. 

So, the idea is to have versioned so name up to subversion number, i.e. libcbang0.so.1.7 presently, to allow bug fixes updates of shared cbang library without the need to rebuild camotics.

Do you have any objections or another vision?

Thank you,
Sergey

[0] https://bugzilla.redhat.com/show_bug.cgi?id=2129303#c2

@jcoffland
Copy link
Member

No objections. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants