On 13 May 2020 at 14:47, Julien Cristau wrote: | Package: libgsl25 | Version: 2.6+dfsg-2 | Severity: normal | | libgsl23 and libgsl25 have a strict (same-version) dependency on | libgslcblas0. This prevents co-installability of different SONAMEs. Is | there a particular reason this strict dependency is necessary (e.g. | internal/private unstable ABI surface that they use)?
I am caught between a rock and a hard place. To _me_ these requests for splitting libgslcblas off never made much sense: AFAICT it is not a full BLAS replacement despite the same, and it is used only by GSL (which is wht the same-version makes sense to me). So I call what you see a feature. OTOH it doesn;t make too much sense to have it distinct packages if we force them. Yet ... if we don;t things may break. I honestly do not know. The packages _do_ come from the same source package; I have maintained GNU GSL for 20 years here and the 'libgslcblas' package never ever had a soname set upstream. It's a weird one. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | [email protected]
