On Thu, Mar 30, 2017 at 01:38:07PM +0100, James Cowgill wrote:
> The correct practice is to rename the package and add no relationships.
> If the SONAME of a library changes then there are no file conflicts and
> the libraries can be co-installed just fine. Using Breaks+Replaces is
> better than Conflicts, but that won't help co-installability.
Right, sorry, I was a tad confused before.
> Unfortunately it's not that easy for gsl because both libgsl0ldbl and
> libgsl2 ship libgslcblas.so.0 so they cannot be co-installed.
In this current case that's not totally true though, while looking at
the current jessie's libgsl0ldbl and stretch's libgsl2, as
libgslcblas.so.0 moved to a multiarch location.
> The
> correct solution would be to move libgslcblas.so.0 into a separate
> package so that at least libgsl2 wouldn't need to conflict with
> libgsl0ldbl. However, that may require a transition if there are any
> users of libgslcblas in the archive.
Right, that would indeed be the best solution.
> Incidentally, I think policy 8.1 prohibits doing what libgsl2 currently
> does (2 libraries in a single package with differently changing SONAMEs).
I fear there are several packages not following of that rule:
https://lintian.debian.org/tags/package-name-doesnt-match-sonames.html
And gsl overrides it:
https://sources.debian.net/src/gsl/2.3%2Bdfsg-1/debian/libgsl2.overrides/
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
Attachment:
signature.asc
Description: PGP signature