[Pkg-javascript-devel] Bug#963039: Bug#963039: node-iconv: versions of nodejs dependencies not properly documented

[Jérémy Lal]

Le ven. 19 juin 2020 à 12:57, Paul Gevers <elbrus at debian.org> a écrit :

> Hi Xavier,
>
> On 19/06/2020 08.07, Xavier wrote:
> > could we solve this by adding a:
> >
> >   Breaks: nodejs (<< ${binary::Version}~)
> >
> > in libnode72 package ? If it works, this will solve the problem for all
> > similar packages.
>
> Are you proposing a solution to the current issue, or is this your long
> term solution? Because if long term, it's a shame that nodejs is coupled
> to the libnode* SONAME (I guess it does solve the current issue). That
> means that there's no gain anymore (from the archive side) to split the
> library into a library binary package that follows the soname. If you
> can't (effectively) co-install the different versions of the libraries,
> you could decide to save yourself the NEW trip on SONAME bumps.
>

libnode68 and libnode72 can be co-installed.
/usr/bin/node is going to load the lib with the SONAME it's been built for.
So of course nodejs 12.x loads libnode72 and nodejs 10.x loads libnode68.
Otherwise the SONAME bump wouldn't be major.

Paul: you're right to point out that it is perfectly possible for another
application
to link against libnode72 without needing to install nodejs 12.

Xavier: i didn't think about that beforehand, but the approach you suggest
will break things (maybe other packages using libv8-dev, for example).

I'm not sure why node-iconv depends on nodejs.
Its autopkgtests should however depend on nodejs >= <version>
where <version> is the one built against the same libnode SONAME as
node-iconv (?)

Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20200619/22f0fe17/attachment.html>