Everything else has gone to mozjs24, it looks like, but polkit still doesn't seem to be compatible with it. Is the port planned?
mozjs24 no longer has a C API, only C++ is supported.
According to http://lists.freedesktop.org/archives/polkit-devel/2014-April/000401.html this is in progress
Hello, Any progress on this?
Kalev, any news on this?
Ok guys, where do we stand on this? This has been in limbo for over a year. On a side note, might I suggest we switch to some other JavaScript engine? I'm trying to get this going on MIPS64, and so far no version of SpiderMonkey seems up to it (even the 31.2 RC). mozjs17 doesn't build for 64-bit in any form without a lot of patching, with the patch effort increasing for every architecture. A lot of this grief could probably be avoided just by switching to a more portable alternative. I'm currently evaluating duktape (http://duktape.org), which so far builds and runs without complaint on MIPS64.
Any news on this? MozJS17 is getting ancient and the build system needs a patch to use new Perl.
A patch has been posted here: https://lists.freedesktop.org/archives/polkit-devel/2016-August/000503.html
(In reply to Jeremy Linton from comment #7) > A patch has been posted here: > > https://lists.freedesktop.org/archives/polkit-devel/2016-August/000503.html Hi :) would it be possible to attach patches here for people not subscribed to the mailing list? Thank you :)
> Hi :) would it be possible to attach patches here for people not subscribed > to the mailing list? Thank you :) They're easy enough to retrieve via the web interface: https://lists.freedesktop.org/archives/polkit-devel/2016-August/000504.html https://lists.freedesktop.org/archives/polkit-devel/2016-August/000505.html https://lists.freedesktop.org/archives/polkit-devel/2016-August/000506.html https://lists.freedesktop.org/archives/polkit-devel/2016-August/000507.html
This has now been committed to master. Thanks, Jeremy!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.