On 16. 11. 25 17:05, Daniel Sahlberg wrote:
Den tis 12 aug. 2025 kl 18:56 skrev notroj (via GitHub) <[email protected]>:notroj opened a new pull request, #34: URL: https://github.com/apache/subversion/pull/34 ``` * configure.ac <http://configure.ac>: Pass complete library version information to libtool via $SVN_LT_SOVERSION, so library filenames are unique to each release rather than constant, while keeping the sonames intact. Examples for SVN 1.14.5: Filename before: libsvn_subr-1.so.0.0.0 Filename after: libsvn_subr-1.so.0.14.5 SONAME before and after: libsvn_subr-1.so.0 ```-- This is an automated message from the Apache Git Service.To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]This has been laying open in GitHub for far too long. Anyone keen on reviewing this? It is unfortunately far out of my comfort zone.
Changing the SOVERSION is a potential backwards-compatibility issue, we can't do this in a patch release. Should be fine to do this on trunk only and release it with 1.15. I think. Someone with more ELF-fu should chime in. Doesn't help that the SONAME is 0 instead of 1, but we can't fix that before 2.0.
We have a similar issue on MacOS, where we set the dylib current-version and compatibility-version both to 1.0.0, but the former could/should be the actual release version.
How does the CMake build do with regards to filenames/sonames?
Has to be done explicitly. CMake has variables to set that globally for a project.
-- Brane
