mozjs24 porting?

[Bastien Nocera]

Hey Kalev,

I was wondering what the status was on:
http://code.google.com/p/libproxy/issues/detail?id=210
and
https://bugs.freedesktop.org/show_bug.cgi?id=74592

Seems that you already managed to get PolicyKit going. Maybe it's time we switched
to the new version so we can remove the old mozjs17 from the repositories.

Cheers

[drago01]

On Fri, Feb 6, 2015 at 11:59 AM, Bastien Nocera  wrote:
> Hey Kalev,
>
> I was wondering what the status was on:
> http://code.google.com/p/libproxy/issues/detail?id=210
> and
> https://bugs.freedesktop.org/show_bug.cgi?id=74592
>
> Seems that you already managed to get PolicyKit going. Maybe it's time we switched
> to the new version so we can remove the old mozjs17 from the repositories.

Does that make any sense to put effort into porting to mozjs24 now
that mozjs31 should be out "soon" ?

[Bastien Nocera]

----- Original Message -----
> On Fri, Feb 6, 2015 at 11:59 AM, Bastien Nocera  wrote:
> > Hey Kalev,
> >
> > I was wondering what the status was on:
> > http://code.google.com/p/libproxy/issues/detail?id=210
> > and
> > https://bugs.freedesktop.org/show_bug.cgi?id=74592
> >
> > Seems that you already managed to get PolicyKit going. Maybe it's time we
> > switched
> > to the new version so we can remove the old mozjs17 from the repositories.
>
> Does that make any sense to put effort into porting to mozjs24 now
> that mozjs31 should be out "soon" ?

It's what's currently used. Presumably, the target would change, and the changes
between mozjs17 and mozjs24 are likely greater than between mozjs24 and mozjs31
(like the fact that there's no C API in newer version, for example).