User:Lkundrak/NodeJS

From FedoraProject

< User:Lkundrak(Difference between revisions)
Jump to: navigation, search
(Created page with '== Packaging node.js in Fedora == Note this is work in progess! node.js is an asynchronous I/O based runtime for v8 javascript. The purpose of this page is to keep track of no...')
 
Line 3: Line 3:
 
Note this is work in progess!
 
Note this is work in progess!
  
node.js is an asynchronous I/O based runtime for v8 javascript.
+
node.js[http://nodejs.org/] is an asynchronous I/O based runtime for v8[http://code.google.com/p/v8/] javascript engine.
  
 
The purpose of this page is to keep track of node.js packaging state, so that it's easy for anyone to to join the efforts and contribute.
 
The purpose of this page is to keep track of node.js packaging state, so that it's easy for anyone to to join the efforts and contribute.
 
It may serve as tracker to aid transparent communication of problems we communicate solve with aid of node.js community outside Fedora (so that they know what bothers us :).
 
It may serve as tracker to aid transparent communication of problems we communicate solve with aid of node.js community outside Fedora (so that they know what bothers us :).
 +
 +
== Versioning ==
 +
 +
Node.js is dependent on v8 and as such, it needs to [[User:Lkundrak/v8|coordinate version updates with v8 package]].
  
 
== Packages and reviews ==
 
== Packages and reviews ==

Revision as of 14:53, 20 December 2010

Contents

Packaging node.js in Fedora

Note this is work in progess!

node.js[1] is an asynchronous I/O based runtime for v8[2] javascript engine.

The purpose of this page is to keep track of node.js packaging state, so that it's easy for anyone to to join the efforts and contribute. It may serve as tracker to aid transparent communication of problems we communicate solve with aid of node.js community outside Fedora (so that they know what bothers us :).

Versioning

Node.js is dependent on v8 and as such, it needs to coordinate version updates with v8 package.

Packages and reviews

Integrating NPM with RPM

  • Does not use pristine upstream sources, not all node.js components in the wild contain package.json
  • Unable to install to different location than what dependencies are dragged from