Node.js 0.6.3 out (npm included)(blog.nodejs.org)
blog.nodejs.org
Node.js 0.6.3 out (npm included)
http://blog.nodejs.org/2011/11/25/node-v0-6-3/
13 comments
What's the state of the art in Debian/Ubuntu packages for Node? Is anyone maintaining some anywhere?
Debian (unstable) - 4.12-1
http://packages.debian.org/sid/nodejs
Ubuntu (11.10) - 0.4.9-1ubuntu3
http://packages.ubuntu.com/oneiric/nodejs
Mint - none
Fedora - none
Arch - 0.6.2-1
http://www.archlinux.org/packages/community/x86_64/nodejs/
Gentoo (unstable) - 0.6.2
http://packages.gentoo.org/package/net-libs/nodejs
OpenSuSE - ??? (couldn't find package database)
FreeBSD - 0.4.12
http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/node/
http://packages.debian.org/sid/nodejs
Ubuntu (11.10) - 0.4.9-1ubuntu3
http://packages.ubuntu.com/oneiric/nodejs
Mint - none
Fedora - none
Arch - 0.6.2-1
http://www.archlinux.org/packages/community/x86_64/nodejs/
Gentoo (unstable) - 0.6.2
http://packages.gentoo.org/package/net-libs/nodejs
OpenSuSE - ??? (couldn't find package database)
FreeBSD - 0.4.12
http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/node/
I maintain a third-party node repo for Fedora:
http://nodejs.tchol.org/
I tried to get it into Fedora proper, but node currently bundles their own slightly modified libev and c-ares, which is against Fedora's packaging policies.
I tried to get it into Fedora proper, but node currently bundles their own slightly modified libev and c-ares, which is against Fedora's packaging policies.
Arch already has 0.6.3: http://www.archlinux.org/packages/community/i686/nodejs/
There is a Ubuntu PPA that tracks Node.js releases pretty closely.
Checked, still at 0.6.2: https://launchpad.net/~chris-lea/+archive/node.js
0.4.12 in Debian unstable.
The npm package has been outdated at 0.2.19 for ages, so this merge will hopefully bring back a usable npm.
The npm package has been outdated at 0.2.19 for ages, so this merge will hopefully bring back a usable npm.
I believe the default version is 0.4.9. This is the output from node -v command on 11.10
You might want to stick with the separate npm for now if you find yourself using "npm help" a lot.