Request for the new version bump :D Maybe with node-waf ? :D
*** Bug 419959 has been marked as a duplicate of this bug. ***
Let's collect all the bump requests in a single bug report.
0.7.10 is out...
0.7.9 is still worth having because 0.7.10 rolled back the V8 requirement to 3.9.24.31, and I've got a Git master installation of Node since chromium:live seems to want >=3.10.2.1, and merging the live ebuild was the surest way of installing that at the time. No rush, but if you get a chance, having any version of node that compiles against dev-lang/v8-9999 and doesn't segfault when being run would be a major plus. Yes, I realize I shouldn't be running a bleeding edge version of a JavaScript engine on my system if all I use it for is Chromium and Node, but I like to keep up with developments in JS runtimes, and my guess is that Node will support V8 >=3.11 very soon now.
oops, s/Node/V8/ in line 2 (or lazily evaluated). Two cups of coffee, a latte, and a get-up-and-go mentality and I'm still a zombie at 6:00PM PDT. Sigh.
+ 12 Jun 2012; Patrick Lauer <patrick@gentoo.org> +nodejs-0.6.19.ebuild: + Bump for #419345 and if I get around to it (or someone provides a patch) I'll hammer in the waffle bits again for 0.7
http://blog.nodejs.org/2012/06/15/version-0-7-11-unstable/ 0.7.11 bump
0.7.12 is up. Current situation is a bit annoying as it blocks unstable chromiums v8 http://blog.nodejs.org/2012/06/19/version-0-7-12/
0.8.0 has been released. Requires v8 3.11.10.10.
(In reply to comment #9) > 0.8.0 has been released. Requires v8 3.11.10.10. here is release notes and changelog http://blog.nodejs.org/2012/06/25/node-v0-8-0/
+ 27 Jun 2012; Patrick Lauer <patrick@gentoo.org> +nodejs-0.7.12.ebuild: + Bump for #419345 #417241 0.8 is in tree but masked until v8 is unmasked.
node 0.8.1 has been released. Requires v8 3.11.10.12
n/m, should have checked the tree. Sorry Patrick, and thanks :-)
http://blog.nodejs.org/2012/07/09/node-v0-8-2-stable/ 0.8.2 is out.
