[Pkg-javascript-devel] Debian Javascript Policy

Jérémy Lal jerry at edagames.com
Sat Oct 15 15:15:36 UTC 2011

On 15/10/2011 15:46, Jonas Smedegaard wrote:
> On 11-10-15 at 11:20am, Jérémy Lal wrote:
>> On 15/10/2011 08:21, David Paleino wrote:
>>> I started a first draft, based on the recent emails, of a 'Debian 
>>> Javascript Policy'. I feel like it's missing lots of things though, 
>>> so any help is much appreciated.
>>> http://wiki.debian.org/Teams/pkg-javascript/Policy
>> Thank you a lot for this.
> Yes, great initiative!
> Since we have now grown to not only do packaging but also formulating 
> Policy, I took the liberty to rename our team page to be more wiki-like 
> (not simply mirroring what was limited by Alioth naming convention):
> http://wiki.debian.org/Javascript
> ...and here is therefore (unsurprisingly) new location of Policy: 
> http://wiki.debian.org/Javascript/Policy
>> We still have to choose if using /usr/share/nodejs as a place to put 
>> native (i mean pure js) node modules is a good idea. It certainly is 
>> not a bad one, but won't it disturb node users ? They are used to find 
>> node modules in something like /usr/lib/node.
> Could you elaborate on the situations that the system path is used 
> directly - as opposed to letting Node resolve it?

AFAIK, never.

> I mean - would any *code* break from using an unusual path in Debian (as 
> is the case e.g. for the issue of renaming the node binary to nodejs), 
> or does it only affect habbits among Node developers manually looking up 
> what is available to them on this machine, while coding?

Yes, you're right.


More information about the Pkg-javascript-devel mailing list