[Pkg-javascript-devel] Javascript team policy and rejection of node-three binary package [and 1 more messages]

[Simon McVittie]

On Sun, 11 Mar 2018 at 14:48:40 +0530, Pirate Praveen wrote:
> On വെള്ളി 09 മാർച്ച് 2018 08:39 വൈകു, Simon McVittie wrote:
> > And for executables, perhaps something like this:
...
> > * should not be named node-* without a suffix like -bin or -tools (?)
> 
> I don't think there is any particular benefit in this restriction.
> Having a uniform was to map node module name -> package name without
> having extra effort to check if it is an executable or library is
> helpful in automation (especially because we are talking about a large
> number of modules here). Manually finding if a module is already
> packaged vs automatically finding.

The reason I suggested that restriction was to avoid having contradictory
requirements: if node-foo is the naming convention for the module
that lets nodejs users require('foo'), and node-foo is also the naming
convention for a nodejs executable that upstream refer to as foo where
foo is too generic for Debian, then we might get a collision between
the requirements for libraries and the requirements for executables.

But perhaps I'm being overly paranoid there, because the main extra
requirement for executables with nodejs as an interpreter is "must depend
on nodejs", and for a package named node-* that's hardly a burden.

    smcv