On Wed, May 22, 2019 at 11:06 AM Jérémy Lal wrote:
>>> Hi Jérémy
>>>
>>> Now that r-cran-v8 seems to be working great with libnode-dev, perhaps
>>> the old libv8 should be removed from sid? Today I was working in sid
>>> and I noticed that apt still prefers the old v8 over the libnode-dev
>>>
Le mer. 22 mai 2019 à 09:36, Jérémy Lal a écrit :
>
>
> Le mer. 22 mai 2019 à 01:32, Jeroen Ooms a écrit :
>
>> Hi Jérémy
>>
>> Now that r-cran-v8 seems to be working great with libnode-dev, perhaps
>> the old libv8 should be removed from sid? Today I was working in sid
>> and I noticed that
Le mer. 22 mai 2019 à 01:32, Jeroen Ooms a écrit :
> Hi Jérémy
>
> Now that r-cran-v8 seems to be working great with libnode-dev, perhaps
> the old libv8 should be removed from sid? Today I was working in sid
> and I noticed that apt still prefers the old v8 over the libnode-dev
> virtual
On Fri, Feb 08, 2019 at 11:48:57AM +0100, Jérémy Lal wrote:
> > That would be absolutely fantastic, yes. Also a symlink from
> > libv8.so-> libnode.so woulde be handy, because libv8 doesn't use
> > pkg-config anywhere else so most bindings just test for linking with
> > -lv8.
> >
>
> Ok then no
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
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
Le ven. 8 févr. 2019 à 15:45, Dylan Aïssi a écrit :
> Hi Andreas,
>
> Le ven. 8 févr. 2019 à 15:39, Andreas Tille a écrit :
> >
> > Dylan, will you find time to have a look? (I don't today and tomorrow -
> later it might be to late ...)
> >
>
> Not sure to understand what you mean. To build
Le ven. 8 févr. 2019 à 13:53, Andreas Tille a écrit :
> On Fri, Feb 08, 2019 at 11:48:57AM +0100, Jérémy Lal wrote:
> > > That would be absolutely fantastic, yes. Also a symlink from
> > > libv8.so-> libnode.so woulde be handy, because libv8 doesn't use
> > > pkg-config anywhere else so most
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, Jeroen Ooms a écrit
> :
> >>
> >> For those following this discussion: there is now a version of
> >> r-cran-v8 that uses libnode-dev in sid. Is
For those following this discussion: there is now a version of
r-cran-v8 that uses libnode-dev in sid. Is there anything we need to
do to get r-cran-v8 back in buster?
On Tue, Jan 29, 2019 at 10:04 AM Andreas Tille wrote:
>
> Hi Jeroen,
>
> I realised that the Debian package of V8 has de facto
On Fri, Feb 8, 2019 at 9:44 AM Jérémy Lal wrote:
>
>
>
> Le ven. 8 févr. 2019 à 07:36, Jeroen Ooms a écrit :
>>
>> For those following this discussion: there is now a version of
>> r-cran-v8 that uses libnode-dev in sid. Is there anything we need to
>> do to get r-cran-v8 back in buster?
>>
>
>
Hi Jeroen,
On Fri, Feb 08, 2019 at 07:36:10AM +0100, Jeroen Ooms wrote:
> For those following this discussion: there is now a version of
> r-cran-v8 that uses libnode-dev in sid.
Thanks a lot for your quick and extremely helpful support.
> Is there anything we need to
> do to get r-cran-v8 back
On Tue, Jan 29, 2019 at 1:04 AM Andreas Tille wrote:
>
> The problem is that the CRAN V8 package has some reverse dependencies
> which all are affected and can not migrate to the next Debian stable
> release which would be a real shame. Do you see any chance to adapt V8
> to some more recent
On Tue, Jan 29, 2019 at 12:15 PM Jonas Smedegaard wrote:
>
> Quoting Jeroen Ooms (2019-01-29 20:11:20)
> > On Tue, Jan 29, 2019 at 10:56 AM Jérémy Lal wrote:
> > >
> > >
> > >
> > > Le mar. 29 janv. 2019 à 19:41, Jeroen Ooms a écrit :
> > >>
> > >> Is there another version of libv8 available on
Quoting Jeroen Ooms (2019-01-29 20:11:20)
> On Tue, Jan 29, 2019 at 10:56 AM Jérémy Lal wrote:
> >
> >
> >
> > Le mar. 29 janv. 2019 à 19:41, Jeroen Ooms a écrit :
> >>
> >> Is there another version of libv8 available on Debian? I'm willing to
> >> try to port it to a newer version of V8. The
Is there another version of libv8 available on Debian? I'm willing to
try to port it to a newer version of V8. The issue with libv8 has
always been that Google refuses to define a stable API, and they do a
new release every day (no joke). So it's very hard to program against
that.
That said,
On Tue, Jan 29, 2019 at 10:56 AM Jérémy Lal wrote:
>
>
>
> Le mar. 29 janv. 2019 à 19:41, Jeroen Ooms a écrit :
>>
>> Is there another version of libv8 available on Debian? I'm willing to
>> try to port it to a newer version of V8. The issue with libv8 has
>> always been that Google refuses to
Le mar. 29 janv. 2019 à 19:41, Jeroen Ooms a écrit :
> Is there another version of libv8 available on Debian? I'm willing to
> try to port it to a newer version of V8. The issue with libv8 has
> always been that Google refuses to define a stable API, and they do a
> new release every day (no
19 matches
Mail list logo
