[GH-ISSUE #167] No soname for ABI tracking #138

New issue

Closed

opened 2026-05-05 11:45:42 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 11:45:42 -06:00

Owner

Originally created by @remicollet on GitHub (Apr 27, 2018).
Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/167

Originally assigned to: @jmcnamara on GitHub.

This library doesn't set any soname, so it is hard to track ABI compatibility

Expected, something like

/usr/lib64/libxlswriter.so -> libxlswriter.so.1
/usr/lib64/libxlswriter.so.1 -> libxlswriter.so.1.0
/usr/lib64/libxlswriter.so.1.0

This means incompatible changes have to bump the soname, new symbols have to bump the minor version.

This a common good practice, respected by nearly all libraries.

Originally created by @remicollet on GitHub (Apr 27, 2018). Original GitHub issue: https://github.com/jmcnamara/libxlsxwriter/issues/167 Originally assigned to: @jmcnamara on GitHub. This library doesn't set any _soname_, so it is hard to track ABI compatibility Expected, something like /usr/lib64/libxlswriter.so -> libxlswriter.so.1 /usr/lib64/libxlswriter.so.1 -> libxlswriter.so.1.0 /usr/lib64/libxlswriter.so.1.0 This means incompatible changes have to bump the soname, new symbols have to bump the minor version. This a common good practice, respected by nearly all libraries.

gitea-mirror

2026-05-05 11:45:42 -06:00

closed this issue
added the
feature request
label

gitea-mirror commented

2026-05-05 11:45:49 -06:00

Author

Owner

@jmcnamara commented on GitHub (Apr 27, 2018):

Good suggestion. I'll look into adding that.

@jmcnamara commented on GitHub (Apr 27, 2018): Good suggestion. I'll look into adding that.

gitea-mirror commented

2026-05-05 11:45:52 -06:00

Author

Owner

@jmcnamara commented on GitHub (Jan 10, 2020):

I still have this at the back of my mind. However, I think there is still too much flux/development going on in libxlsxwriter to try stabilise the ABI or use semantic versioning.

@jmcnamara commented on GitHub (Jan 10, 2020): I still have this at the back of my mind. However, I think there is still too much flux/development going on in libxlsxwriter to try stabilise the ABI or use semantic versioning.

gitea-mirror commented

2026-05-05 11:45:54 -06:00

Author

Owner

@jmcnamara commented on GitHub (Sep 21, 2020):

Same comment as above. Libxlsxwriter still has too much change to try stabilise the ABI. Closing for now.

@jmcnamara commented on GitHub (Sep 21, 2020): Same comment as above. Libxlsxwriter still has too much change to try stabilise the ABI. Closing for now.

gitea-mirror commented

2026-05-05 11:45:57 -06:00

Author

Owner

@imaiguo commented on GitHub (Jun 2, 2021):

need soname urgently

@imaiguo commented on GitHub (Jun 2, 2021): need soname urgently

gitea-mirror commented

2026-05-05 11:45:59 -06:00

Author

Owner

@jmcnamara commented on GitHub (Jun 2, 2021):