On March 4, 2018 3:15:24 AM GMT+05:30, Simon McVittie <s...@debian.org> wrote: >Am I right in saying that nodejs-handlebars (or libjs-handlebars or >some >such) contains both a command-line tool, handlebars(1) (or similar), >and >a library named handlebars for node.js?
Yes. handlebars binary package includes /use/bin/handlebars and /usr/lib/nodejs/handlebars >If I understand correctly, best practice for such libraries in other >languages (mandatory for C and recommended for Python/Perl/etc.) is >that >the command-line tool is a separate binary package, for better >discoverability (and in the case of Python, to avoid causing random >breakage for users of the command-line tool if it originally used the >Python 2 interpreter and gets moved to Python 3 later). > >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. But it was not acceptable to waldi, when discussing over irc. It was eventually accepted by another ftp master, but I think it better to clarify this situation in policy. I have provided links to irc discussion in my first mail to this thread. > smcv -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
