Downstream .so name versioning
In cases where upstream ships unversioned .so library (so this is not needed for plugins, drivers, etc.), the packager MUST try to convince upstream to start versioning it.
If tjat fails due to unwilling or unresposive upstream, the packager may start versioning downstream but this must be done with caution and ideally only in rare cases. We don't want to create a library that could conflict with upstream if they later start providing versioned shared libraries. Under no cicumstances should the unversioned library should be shipped in Fedora.
For downstream versioning, the name should be composed like this:
The n should initially be a small integer (for instance, "1"). Do not forget to add the SONAME field (see below) to the library.
When new versions of the library are released, you should use the
tool to check for differences in the build shared
libraries, and if it detects any incompatibilities, bump the n number by one.
When running an executable linked to shared object with SONAME field, the dynamic linker check for this field instead of filename to determine which object to link with. This allows developers to simply link against the unversioned library symlink and the dynamic linker will still links against the correct object.
Keep in mind that altough the SONAME and the filename should be the same, the
SONAME field actually matters when dynamically linking. The dynamic linker also
does only simple equality check on the field and do not check for ABI
incompatibilities and similar problems. This is the main reason for using the
tool and the name bumping.
$ gcc $CFLAGS -Wl,-soname,libfoo.so.0.n -o libfoo.so.0.n
$ objdump -p /path/to/libfoo.so.0.n | grep 'SONAME'