On 22/11/2024 19:02, Andrey Rakhmatullin wrote:
On Fri, Nov 22, 2024 at 11:09:04AM +0000, Ahmad Khalifa wrote:
I don't see a rule prohibiting that
Public shared libraries must be installed in a package with the name based
on the library SONAME (see Policy 8.1; you must read the whole of Policy 8
when packaging a public shared library). Even if it's fine for your
package (so the tool is less important than the library), packages with
different SONAMEs of the same library should be co-installable.
I was thinking the tool is more important than the library and chapter 8
starts off by saying "Shared libraries that are internal to a particular
package [...] are not subject to its requirements."
But it seems safer to split them regardless of how unlikely it is to be
used since there aren't lots of examples.
--
Regards,
Ahmad
