Skip to content

Upstream .so name versioning? #249

@robert-scheck

Description

@robert-scheck

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.

Quoting from section "SONAME handling" from https://docs.fedoraproject.org/en-US/packaging-guidelines/#_downstream_so_name_versioning:

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:

$ gcc $CFLAGS -Wl,-soname,libfoo.so.0.n -o libfoo.so.0.n

If you want to check if the SONAME field is set and what value it has, use the objdump command (from binutils):

$ objdump -p /path/to/libfoo.so.0.n | grep 'SONAME'

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions