[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1001541: run-time shared lib not placed in package with proper name

Hi Tobias,

* Tobias Hansen <thansen@debian.org> [2022-01-10 20:49]:
from debian/README.Debian:

"The libecl.so file is changing too quickly and
is integrated with the ecl binary to such extend
that, after consultation with upstream,  I will
not create a libecl package.

If ecl will reach a stable release (1.0 or so) and
some guarantees with respect to API stability
can be make I will reconsider this decision."

This is still true 13 years later. ecl is using its version (which is based on the year) as SONAME...

And sagemath is not unrelated software: maxima-sage and sagemath are the only packages in Debian with Depends: ecl. We are always making sure that maxima-sage and sagemath are rebuilt with every new ecl version, however sagemath 9.2 in Debian was already so broken that it didn't matter (look at the number of bugs fixed by sagemath 9.4-1).

Creating a library package for ecl would just mean that it would have to go through NEW for every new version with no real benefit.

Do you insist that I do that?

according to policy:

"The run-time shared library must be placed in a package whose name
changes whenever the SONAME of the shared library changes."


This is a must according to our policy and not a question on what someone insist on. Note that the policy also advices for libraries that are fast moving, for example by using a static library. Though looking at the recent changelog I think it should be fine to go through new every other year, I usually find it quiet fast.

Cheers Jochen

Attachment: signature.asc
Description: PGP signature

Reply to: