[Pkg-javascript-devel] Naming node packages with binaries

[Jonas Smedegaard]

Quoting Leo Iannacone (2014-05-08 19:38:57)
> AFAIK.. when a binary is present in a package, the package should have 
> the be named as the binary.

If code project is _mainly_ that binary, then yes.  But for project 
known and "Shit" with binary "the_shit", I'd name the package "shit".


> But.. this is not so clear for node modules.
> 
> For instance, for mocha, according with javascript policy, I should 
> ship a package called `node-mocha' rather than one simply called 
> `mocha'.
> 
> This seems to be in contrast with perl policy (I think with python 
> too).
> 
> Should we follow this cli_based_name policy and rename those packages 
> having binaries ?

Sure - node-* name is for node _modules_, not anything-related-to-node.


> David Prevot suggests in chan:
> <taffit> maybe a "Provides: node-$stuff" could help in the dependency
> chain if needed

Yes, if code project is mainly a binary but also a Nodejs module.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/attachments/20140508/73884b19/attachment-0001.sig>