(reordered your reply to the bottom)

On 15/09/16 19:22, Jonas Smedegaard wrote:
> > Quoting Jérémy Lal (2016-09-15 17:21:30)
> >> 2016-09-15 17:12 GMT+02:00 Matijs van Zuijlen <mat...@matijs.net>:
> >>
> >>> Package: npm
> >>> Version: 1.4.21+ds-2
> >>> Severity: wishlist
> >>>
> >>> Executables installed with npm need the /usr/bin/node executable, which
> >>> is provided in the nodejs-legacy package. This information is currently
> >>> only in the README.Debian file. I think it would be really helpful to
> >>> add nodejs-legacy to the npm package's Suggests:, or even Recommends:.
> >>>
> >>>
> >> Well, re-reading
> >> https://lists.debian.org/debian-devel-announce/2012/07/msg00002.html
> >> paragraph 2 says
> >>
> >>> No package in the archive may depend on or recommend
> >>> the nodejs-legacy package, which is provided solely for upstream
> >> compatibility.
> >>
> >> Taken literally, it doesn't forbid Suggest. Does it ?
> >
> > I agree we are not forbidden from suggesting: Seems to me the choice of
> > words by the Technical Committee was deliberate, as that matches how
> > packages outside of Debian (i.e. non-free stuff) is allowed to be
> > suggested only.
>

2016-09-16 9:57 GMT+02:00 Matijs van Zuijlen <mat...@matijs.net>:

> I read through bug 614907, and I think the very best solution would be
> for npm to ensure the correct node executable is referenced in each
> package's executable. I don't know how feasible that would be.
>

While it looks pleasant, the executable name is referenced in js code, in
makefiles,
bash files, json files, and possibly in very hidden ways.
It wouldn't be the best solution, it would be the riskiest one.

Jérémy
-- 
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to