On Saturday 2022-12-10 19:04, John Paul Adrian Glaubitz wrote:
Yes, OK. However, openSUSE does seem to use three-digit ABI version numbers when other distributions don't. This is what confused me.
For example, the current version of libprotobuf:
- openSUSE - libprotobuf3_21_11 - Debian/Ubuntu - libprotobuf32 - Mageia - libprotobuf30
Someone cherry-picked some git commit or something that changed -version-info to -release. From 15daef3b7912b9434955a8614e018de00591aefb Mon Sep 17 00:00:00 2001 From: Deanna Garcia <deannagarcia@google.com> Date: Wed, 3 Aug 2022 17:40:03 +0000 Subject: [PATCH 1/2] Use release version instead of libtool version [ 332s] libtool: install: /usr/bin/install -c .libs/libprotobuf-3.21.11.so
Or libimobiledevice:
- openSUSE - libimobiledevice-1_0-6 - Debian/Ubuntu - libimobiledevice6 - Mageia - libimobiledevice - Fedora - libimobiledevice
openSUSE build log: -pthread -Wl,-soname -Wl,libimobiledevice-1.0.so.6 Debian just does not give a lot of care to its package naming here. If there was both a libimobiledevice-1.0.so.6 and a libimobiledevice-2.0.so.6 file, there'd be a problem on Debian. Fedora does not care about SLPP at all.
Or libavcodec from ffmpeg:
- openSUSE - libavformat58_76 - Debian/Ubuntu - libavcodec58 - Fedora - libavcodec-free
Like case 1 above. When the SONAME changes via a patch for any particular reason, the package build recipe has to follow suit.