Re: Replacing polkit JS backend

2017-10-20 Thread Ikey Doherty
OK I've got some initial rough patchwork hovering on GitHub: https://github.com/ikeydoherty/polkit-no-script/tree/noscript-3 https://github.com/ikeydoherty/polkit-no-script/commit/5bcb1c1f9f678d950c44eccba81db36fddb09efc I've opted to make it an **alternative** backend to ease migration, thus:

Re: Replacing polkit JS backend

2017-10-20 Thread Ikey Doherty
Cheers! On 20/10/17 17:29, Jeremy Linton wrote: > Hi, > > As a short term solution, there are patches to move to to mozjs38. > > https://www.mail-archive.com/polkit-devel@lists.freedesktop.org/msg00499.html > > > I've recently been encouraged to do the port to mozjs52 as well, > although my pe

Re: Replacing polkit JS backend

2017-10-20 Thread Jeremy Linton
Hi, As a short term solution, there are patches to move to to mozjs38. https://www.mail-archive.com/polkit-devel@lists.freedesktop.org/msg00499.html I've recently been encouraged to do the port to mozjs52 as well, although my personal opinion is that javascript is way overkill for what polkit

Re: Replacing polkit JS backend

2017-10-20 Thread Ikey Doherty
Replying -> On 20/10/17 17:20, Simon McVittie wrote: > On Fri, 20 Oct 2017 at 16:57:55 +0100, Ikey Doherty wrote: >> however the fact remains right now of nuking the dead mozjs >> implementations actively from Solus, mozjs17 was dropped, now mozjs185 >> is kicked out (super dead) and git only supp

Re: Replacing polkit JS backend

2017-10-20 Thread Simon McVittie
On Fri, 20 Oct 2017 at 16:57:55 +0100, Ikey Doherty wrote: > however the fact remains right now of nuking the dead mozjs > implementations actively from Solus, mozjs17 was dropped, now mozjs185 > is kicked out (super dead) and git only supports mozjs24, again, very > dead. We're only allowing 38 +

Re: Replacing polkit JS backend

2017-10-20 Thread Ikey Doherty
On 20/10/17 16:49, Simon McVittie wrote: > On Fri, 20 Oct 2017 at 16:10:24 +0100, Ikey Doherty wrote: >> Our intention is that when this work is complete and tested in Solus, >> we'll want to upstream this. > > (For avoidance of doubt, I do not consider myself to be a polkit > maintainer and am

Re: Replacing polkit JS backend

2017-10-20 Thread Simon McVittie
On Fri, 20 Oct 2017 at 16:10:24 +0100, Ikey Doherty wrote: > Our intention is that when this work is complete and tested in Solus, > we'll want to upstream this. (For avoidance of doubt, I do not consider myself to be a polkit maintainer and am not in a position to accept or reject your design pro

Replacing polkit JS backend

2017-10-20 Thread Ikey Doherty
Hi, I'm Ikey Doherty, leader of the Solus project [1]. Yep, I know, yet another thread about replacing mozjs in polkit! Anyway, we've opted to tear out the existing JS backend entirely in Solus [2] - but we're not putting any JS providers back in. Instead we're going with a simpler, statically de