Re: [Pkg-javascript-devel] Javascript team policy and rejection of node-three binary package

[Ian Jackson <ijackson@chiark.greenend.org.uk>]

Pirate Praveen writes ("Re: [Pkg-javascript-devel] Javascript team policy and rejection of node-three binary package"):
> On March 4, 2018 3:15:24 AM GMT+05:30, Simon McVittie <smcv@debian.org> wrote:
> >For instance, src:tap.py builds python3-tap (the Python 3 library for
> >"import tap"), python-tap (the Python 2 library for "import tap") and
> >tappy (the tappy(1) command). If you did similar things for JavaScript,
> >you could have a handlebars package that depends on libjs-handlebars
> >and nodejs?
> 
> Yes, that is what I did.

Simon is asking the same questions as I was earlier.  Sorry for
posting before reading the whole thread.

Is this going to be common ?  The Javascript ecosystem has large
numbers of small packages - but do they mostly contain just JS
libraries or do they generally all contain command line utilities
too ?

If only a much smaller number of upstream packages have command line
utilities, then we could have the number of JS .deb packages that need
to be maintained by putting the node and browser files into the same
package.

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.