Hello team members,
I'm still struggling in packaging TileMill for Debian. After the whole bunch of
node-* packages I uploaded, I hoped everything went fine, when... TileMill
requires an older version of a package I uploaded (node-bones 1.3.* vs. the
Debianic 2.0).

Now, I don't know what to do. Should I make a node-bones1 package? Should we
establish some policy for keeping different versions of a package?
It would be nice if we could use the same hierarchy of ~/.node_modules/ or
~/.npm/ in our NODE_PATH, i.e. something along the lines of:

\ -- module/
     | --- 0.1/
     | --- 0.2/
     \ --- .../


| -- module@0.1/
| -- module@0.2/
\ -- module@.../

Or, at least, @1.x/, @2.x/, ... .

I can't think of any other way of keeping things sane, other than patching all
apps to work with the packaged modules (in this case I'll stop right away
working on TileMill, it's too far away from my possibilities), or bundling the
needed modules in the orig tarball.

What's your opinion on this?

Thank you,
 . ''`.   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

Attachment: signature.asc
Description: PGP signature

Pkg-javascript-devel mailing list

Reply via email to