On Thursday, May 14, 2026 5:33:00 PM Central European Summer Time Russ Allbery wrote: > > 1. It is not needed to change package names for this. One can also use > > "Provides: <something-that-changes-with-soname>" and have packages > > depend on that. > > I don't understand this objection. The reason why the name of the package > needs to change is that for a normal upgrade transition that doesn't > require a lockstep upgrade, you have to be able to install version 1 and > version 2 (SONAMEs) of the library at the same time, and the only way that > is possible in Debian's packaging system is if either they are both > included in the same package (usually not a good idea since the different > versions come from different versions of the source package, and certainly > not the common approach) or if the package name is different.
But sometimes you don't want to. Especially if the libraries are not using symbol versioning and the libraries are likely to be loaded into the same process. > > Provides is of no help here whatsoever so far as I can see. What am I > missing? You can do a lot of magic with shlibs/symbols files and provides e.g. you can in your symbols/shlibs file specify libfoo (>>VERSION), libfoo-abi-7 and have libfoo provide libfoo-abi-7. We have done that for libraries with exported-symbols-that-shouldn't-be-used- unless-you-are-special; see for example the qt6-base source package. It is also used for the kdepim (personal information management: email,contacts,calendar,...) which has a lot of shared components without a stable abi and from an upstream POV it is considered one release that just comes in multiple tarballs. /Sune -- I didn’t stop pretending when I became an adult, it’s just that when I was a kid I was pretending that I fit into the rules and structures of this world. And now that I’m an adult, I pretend that those rules and structures exist. - zefrank
signature.asc
Description: This is a digitally signed message part.
