Guillem Jover <[email protected]> writes: > When a package ships multiple shared libraries (usually a bad idea), > it's okish as long as they use the same SOVERSION. In case they have > different SOVERSIONs and as such are out of step, there's no guarantee > they will not be changed in the future too, in which case the package > would need its name to be bumped, but only due to part of the contents, > some packages might need to be unneedingly rebuilt, or what's more > common, the package will end up not being renamed, and ABI issues will > crop up.
> Please add a new check to emit an error in case there's several shared > libraries with different SOVERSIONs. This should also avoid false > positives on stuff like glib. One of the main reasons why I'd been hesitant historically to do this is that I was worried about encouraging library maintainers to do complex transitions for existing shared library packages that don't follow this rule. Converting from multiple shared libraries in one package to multiple packages, one per shared library, when there hasn't been an SONAME change was surprisingly difficult to get right. But maybe we can handle that by just adding a long explanation to the tag description. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
