On 12/10/22 10:09, Andrei Borzenkov wrote:
May be you should start with own guidelines instead of referring to the third-party posts
https://en.opensuse.org/openSUSE:Shared_library_packaging_policy#Package_nam...
...
What's the point in changing the package name when the ABI change is a compatible one? https://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html (see Section 3.6) The whole point of encoding the SOVERSION in the package name is to indicate whether two versions of a shared library have a compatible ABI or not. That's also the reason why there is a libfoo.so.1 even when the full version is 1.2.3. This is also true for
libcdrdeflt1_0 libmythes-1_2-0 libpng16-16
just the first several random libraries installed here.
Three examples out of how many?
I do not mean that your recommendation was incorrect. But it is also important to understand *why* library package has to be named this way for the future. The reason "because it needs just major number" is not correct from the packaging point of view. It may be relevant for developer to chose the SONAME.
Again, the point of using SONAME is to indicate whether two library packages are ABI-compatible. If that above SCSI library ABI version changes from 0.2.0 to 0.3.0 without breaking the ABI, it makes no sense to bump the ABI version for that. Adrian