Polkit on Duktape

[Jasper St. Pierre]

So, where did we get with this?

 * JavaScript rules are (somewhat) a failure, but it's not something
we can back out of easily, because doing that could break people who
rely on JS rules, causing a gap where rules aren't being applied. Not
a good situation to be in. Going back to PKLA rules might also mean
that someone who can't express complex ACL logic in those rules means
that they reinvent polkit in their app.

 * Even though mozjs isn't getting new stable standalone releases, the
fact that it's been more "battle-tested" than Duktape means that it's
still a better pick. Even though it's much slower for our use-case and
much more complex than it needs to be.

Is that a good summary?

On Fri, Aug 14, 2015 at 1:14 AM, Nikos Mavrogiannopoulos
<nmav at redhat.com> wrote:
> On Thu, 2015-08-13 at 12:31 -0700, Jasper St. Pierre wrote:
>
>> > hasn't
>> > been updated to a new upstream version since 2012, caused test
>> > failures
>> > when updated (until recently),
>> Well, if updating to a newer version causes test issues, how would
>> unbundling libraries fix that?
>
> Most likely in the sense that issues will be noticed and fixed as early
> as possible, as opposed to trying to solve a bunch of accumulated
> issues in a much longer period.
>
> regards,
> Nikos
>



-- 
  Jasper