[Pkg-javascript-devel] Node app requiring "general" javascript library

[David Paleino]

On Thu, 13 Oct 2011 21:00:02 +0200, Jonas Smedegaard wrote:

> Hmm - looking closer at this issue, it seems more appropriate to provide 
> a separate binary package: When used with Node it should depend on 
> libnode, but used without it is bothersome to have libnode pulled in.

That's another question I have: I haven't understood which exact runtime
depends do libnode-* packages need. I've added other libnode-* or libjs-* but,
for example, I don't know whether it makes sense to depend on nodejs or other
related packages.

> Same for backbone.  Which might solve that issue I raised in a separate 
> thread: Maybe best that packages usable both alone and with Node is 
> provided as two separate binary packages, not so much to save space 
> (these are all typically tiny packages) but to avoid dependency hell.

Well, the libnode-* could just provide a symlink to the file contained in the
libjs-* (or the other way around). It causes a bit of packaging overhead, but
seems acceptable (at the end of the day, it's probably just a new stanza in
d/control, and a d/libnode-*.links)

David

-- 
 . ''`.   Debian developer | http://wiki.debian.org/DavidPaleino
 : :'  : Linuxer #334216 --|-- http://www.hanskalabs.net/
 `. `'`  GPG: 1392B174 ----|---- http://deb.li/dapal
   `-   2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/attachments/20111013/ad9fa08b/attachment-0001.pgp>