On Monday, 11 February 2019 09:51:11 CET Jérémy Lal wrote:
> that's what i tried to do in the first place.
> However, the lack of v8 soname and abi stability across versions gave me so
> much additional work that i ended up not doing it at all, leading to v8
> being unmaintained. The solution here
Le lun. 11 févr. 2019 à 09:11, Dominique Dumont a écrit :
> Hi
>
> On Friday, 8 February 2019 12:10:01 CET Jérémy Lal wrote:
> > > I suppose i need to ask a removal of libv8 from unstable (it's removed
> > > from testing) to
> > > be able to "take" libv8-dev. Or maybe declare a libv8-in-nodejs-de
Hi
On Friday, 8 February 2019 12:10:01 CET Jérémy Lal wrote:
> > I suppose i need to ask a removal of libv8 from unstable (it's removed
> > from testing) to
> > be able to "take" libv8-dev. Or maybe declare a libv8-in-nodejs-dev
> > package ?
> > In any case i don't know if i should make a libv8-x
cc-ing to -devel, because advices about libraries are scarce in javascript
land.
Le ven. 8 févr. 2019 à 11:48, Jérémy Lal a écrit :
> Le ven. 8 févr. 2019 à 10:31, Jeroen Ooms a écrit :
>
>> On Fri, Feb 8, 2019 at 9:44 AM Jérémy Lal wrote:
>> >
>> >
>> >
>> > Le ven. 8 févr. 2019 à 07:36, Jero
4 matches
Mail list logo
