-
Notifications
You must be signed in to change notification settings - Fork 854
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 Versioning #927
Comments
Can you send a PR for this? |
#930 is the start of what needs to change. I haven't figured out the pybind11 one yet. Any thoughts? |
@christian-rauch okay, the PR is passing testing and all of the Fedora SONAME checks are passing. This should be ready for review. |
Fixed by #930. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to configure proper soname's and versioning for downstream packaging policy compliance. The goal is to provide an ABI guarantee for any given soname. This can be accomplished by soname versioning or library symbol versioning. The simpler solution is likely the right one. Soname bumps are usually more involved and will require rebuilding all linked packages.
Fedora: https://docs.fedoraproject.org/en-US/packaging-guidelines/C_and_C++/
Debian: https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#library
Based on the fedora-review tool, there are 15 sonames that need addressing:
The text was updated successfully, but these errors were encountered: