On Mon, Aug 19, 2019 at 5:54 PM Brian J. Murrell brian@interlinx.bc.ca wrote:
I've been unable to locate any packaging guidelines/requirements that indicate that a source package providing shared libraries should have those shared libraries packaged into a sub-package with the major version of library appended to the sub-package name (i.e. libfoo1, libfoo2, etc.) -- to facilitate concurrent installation of the differing major versions of the library.
Is there no such guideline/requirement?
Sounds more like the Debian way of packaging shared objects, but it doesn't solve the resulting conflict on libfoo.so in devel packages.
There is a guideline for a -lib or -libs sub-package if the libraries may be usable without the whole package, if I remember correctly.
Dridi