On 19/11/2011 18:51, David Paleino wrote:
> 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:
> 
> /usr/lib/nodejs/
> \ -- module/
>      | --- 0.1/
>      | --- 0.2/
>      \ --- .../
> 
> or:
> 
> /usr/lib/nodejs/
> | -- 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?

Please do NOT follow that path !

I'll help you with patching TileMill to it runs well with bones 2.0
It looks very easy to do :
https://github.com/developmentseed/bones/blob/master/CHANGELOG.md

We'll send a patch to TileMill upstream to it supports latest bones.

Jérémy.

_______________________________________________
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to