[Pkg-javascript-devel] Status of libv8?

[Jérémy Lal]

Le ven. 18 janv. 2019 à 18:39, Andreas Tille <andreas at an3as.eu> a écrit :

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

Yes, i will have a look at this. I have no idea how, for now.

Jérémy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20190118/c89b0704/attachment.html>