On ഞായര്‍ 11 മാർച്ച് 2018 04:59 വൈകു, Simon McVittie wrote:
> 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.

In case of conflict, we can add js suffix to the executable. node ->
nodejs, babel -> babeljs.

The binary can be foo (since it has foo command) and it can provide
node-foo (since require 'foo' works).

Attachment: signature.asc
Description: OpenPGP digital signature

Pkg-javascript-devel mailing list

Reply via email to