Update nodejs

[pigfoot]

No description provided.

[lluixhi]

Just a note, that libressl patch is still broken. The crypto stuff works, but some TLS tests still fail.

[blueness]

i'd rather not push something broken to the overlay.

[pigfoot]

Understood. It makes sense.

[soredake]

nodejs/node#9376

[dorvan]

please fix this!!!!!

[jbergstroem]

I think the best course of action wrt libressl is to not support it at all at the moment.

[jbergstroem]

This should probably target v6 (new LTS) and v7 as well. deps needs to be bumped.

[dorvan]

so it's not possible in libressl gentoo system use nodejs? any workaround?

[jbergstroem]

@dorvan the current state of libressl support in node.js is a very fresh patch that makes it build but also disables some functionality. You will likely also have issues with a system that has both libressl and openssl installed from npm or the test suite (makes assumptions about openssl). What I'm saying is that I think its a bit premature to just include the patch that makes it build and "be done with it". I guess it could be part of a masked package so people can test it out.

[dorvan]

@jbergstroem my comment it's not regarding nodejs in the gentoo/libressl project, but on other distros libressl implementation it's a production reality not only on nodejs but on another problematic/core deps/frequently used packages. looking to frequently used and state-of-art or mainstream packages thay need a priority and a stability about the system profile coherence. Otherwise the risk is to remake the same quest of perl and python migration of 2004/2007 before the definitive design of system infrastructure with python eselect switch (causing looses in community on both developers and users side). or libressl migration can be more "flexible" where openssl and libress can find place on the same system, switching application(for package)/library with an eselect or have to be more convinced and fast. other ways can be like the icu lib update that impacts of the functionalities and coherence of all the installed system, make it broken with any simple maintenance action.

[jbergstroem]

@dorvan: I'm not sure what you're talking about. All I'm trying to to is to explain the current level of support for libressl in node since I happen to have a pretty good insight in that situation (being a node.js developer and part of the build infra team).

[ghost]

As an alternative you can use the bundled openssl, but some people say that this is not safe(?). For me is ok though, if we keep updating regularly.

Check my overlay for nodejs ebuilds, which has the bundled-ssl USE flag. It's based on the PR made by @soredake in the link above.

[pigfoot]

Close due to #154