<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr">Le ven. 18 janv. 2019 à 18:39, Andreas Tille <<a href="mailto:andreas@an3as.eu">andreas@an3as.eu</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Fri, Jan 18, 2019 at 01:46:13PM +0100, Jérémy Lal wrote:<br>
> Le ven. 18 janv. 2019 à 13:04, Andreas Tille <<a href="mailto:andreas@an3as.eu" target="_blank">andreas@an3as.eu</a>> a écrit :<br>
> > ><br>
> > > Possible solutions (besides not using it at all):<br>
> > > - bundle it - nodejs bundles it<br>
> > > - change nodejs to build its v8 as a shared lib, and provide it<br>
> > > it makes sense because upstream nodejs do all the work of keeping ABI<br>
> > > stability,<br>
> > > backporting security fixes, choosing the right version, and so on.<br>
> > > - take over maintenance and distribute it independently of nodejs<br>
> ><br>
> > This sounds like a pretty sensible solution. I see you and Jonas are<br>
> > also uploaders for nodejs. It would be really great if you could do<br>
> > this.<br>
> ><br>
> Which one ?<br>
<br>
I'd prefer<br>
<br>
- change nodejs to build its v8 as a shared lib, and provide it <br>
it makes sense because upstream nodejs do all the work of keeping ABI <br>
stability,<br>
<br>
I admit I do not fully understand what you mean by<br>
<br>
- bundle it - nodejs bundles it<br>
<br>
(sounds similar to what you write above.<br>
<br>
I think the "take over maintenance and distribute it" has no real future<br>
considering that an RC bug in libv8 did not even received an answer. I<br>
guess the reason for this is that you have other things to play with. ;-)<br>
<br>
> Also i won't upload new nodejs versions until it goes to testing, of course.<br>
<br>
What about experimental for the moment?<br></blockquote><div><br></div><div>Yes, i will have a look at this. I have no idea how, for now.</div><div><br></div><div>Jérémy</div></div></div>