You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of writing, there doesn't seem to be proper upstream .so name versioning in re. Yes, I'm aware there is something like LIB_SUFFIX=.so.0, but this unfortunately has nothing to do with proper .so name versioning, as the SONAME is still libre.so rather libre.so.0. Yes, even this can be worked around by passing some arguments like SH_LFLAGS="-shared -Wl,-soname,libre.so.0", but this still doesn't let downstreams know whether the old and the new version are ABI compatible or not, thus this should be IMHO really handled by upstream.
The SONAME field is written to the shared object by linker, using (at least in case of ld) the -soname SONAME flags. This can be passed as an option to gcc like this:
Please note that this issue is also meant as very kind try to convince you as upstream to start versioning your .so library (as our Fedora Packaging Guidelines request).
The text was updated successfully, but these errors were encountered:
As of writing, there doesn't seem to be proper upstream .so name versioning in re. Yes, I'm aware there is something like
LIB_SUFFIX=.so.0
, but this unfortunately has nothing to do with proper .so name versioning, as the SONAME is stilllibre.so
ratherlibre.so.0
. Yes, even this can be worked around by passing some arguments likeSH_LFLAGS="-shared -Wl,-soname,libre.so.0"
, but this still doesn't let downstreams know whether the old and the new version are ABI compatible or not, thus this should be IMHO really handled by upstream.Quoting from section "SONAME handling" from https://docs.fedoraproject.org/en-US/packaging-guidelines/#_downstream_so_name_versioning:
Please note that this issue is also meant as very kind try to convince you as upstream to start versioning your .so library (as our Fedora Packaging Guidelines request).
The text was updated successfully, but these errors were encountered: