move to saner SONAME
Issue #51
new
Currently, each release has its own SONAME so no two releases are binary compatible. However, the ABI doesn't change much and we can move to a more stable SONAME.
Comments (4)
-
-
reporter I've reported it to M4RIE as well https://bitbucket.org/malb/m4rie/issue/16/move-to-saner-soname
-
Is this still an issue?
-
reporter We didn’t do anything here, so it’s unfortunately still an issue.
- Log in to comment
This is really import for Linux distributions. We are currently updating all the Sage dependencies in Debian [¹] and for M4RI/M4RIE it is especially important to have a sane SONAME, because other libraries (e.g. linbox) depend on it. So right now M4RI claims not only to break its own ABI with every update, but also the ABIs of the libraries depending on it (and they need a source upload with every M4RI update). Does this also have to be reported for M4RIE or are they handled together?
[1] http://wiki.debian.org/DebianScience/Sage