All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Adam Duskett <aduskett@gmail.com>
Cc: Marek Belisko <marek.belisko@open-nandra.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	buildroot@buildroot.org,
	Giulio Benetti <giulio.benetti@benettiengineering.com>,
	Norbert Lange <nolange79@gmail.com>,
	Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
Subject: Re: [Buildroot] [PATCH v2 1/4] package/polkit: bump version to 0.119 and use duktape
Date: Sat, 24 Jul 2021 23:30:29 +0200	[thread overview]
Message-ID: <20210724233029.0b6e4d2f@windsurf> (raw)
In-Reply-To: <20210721214518.227254-1-aduskett@gmail.com>

On Wed, 21 Jul 2021 14:45:15 -0700
Adam Duskett <aduskett@gmail.com> wrote:

> Unfortuantly, as of commit 3e1d61868fa8bfc586099302e931433270e5d17d, polkit
> requires mozjs >= 78, which means spidermonkey is too old. As such, this patch
> is larger than usual.
> 
> Spidermonkey has a few major issues:
>   - The source directory after compilation is enormous (2.7G!)
>   - The shared library is 24MB stripped!
>   - It requires python2 to build, which is EOLed, and Buildroot is working
>     towards removing. See: https://elinux.org/Buildroot:Python2Packages
> 
> Instead of going through the arduous task of updating Spidermonkey, there is a
> better solution: use duktape.
> 
> There has been a pending patch for over a year that incorporates duktape as an
> optional backend for polkit found here:
> https://gitlab.freedesktop.org/polkit/polkit/-/merge_requests/35
> 
> As Thomas Petazzoni put it:
>   "As I am subscribed to notifications on this merge request, I have been
>   following the intermittent discussions taking place on this topic.
>   And indeed, discussions have been sparse, and the polkit maintainer reaction
>   has not been very supportive. It even feels like they are trying to find
>   every possible argument or small issue not to merge the duktape integration."
> 
> Many people have come out to support using duktape, and many users, including
> myself, have used polkit with duktape for as long as the above merge request has
> been around without issues; merging in the above merge request is an acceptable
> exception to the typical Buildroot package policies.
> 
> As Thomas also suggested, I have forked polkit on Github
> (https://github.com/aduskett/polkit-duktape), with the above duktape
> merge request applied, and a release made with the same tag as upstream (0.119).
> 
> I refrained from also adding 0001-make-netgroup-support-optional.patch as it is
> outside of the scope of why the fork exists.
> 
> Changes:
>   - refactor 0001-make-netgroup-support-optional.patch to work with 0.119 and
>     duktape.
>   - Remove upstream incorporated 0002-jsauthority-memleak.patch
>   - Remove upstream 0003-polkit-0.116-pkttyagent-sigttou-bg-job.patch
>   - Remove any trace of spidermonkey from polkit, udisks, and systemd-polkit
>   - Add duktape as a dependency of polkit
>   - Change POLKIT_SITE to the above polkit-duktape GitHub repository.
> 
> Signed-off-by: Adam Duskett <aduskett@gmail.com>

Thanks a lot for this new iteration, I have applied the entire series
to master. Thanks for this work, it's really great to have that in
Buildroot now.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

      parent reply	other threads:[~2021-07-24 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 21:45 [Buildroot] [PATCH v2 1/4] package/polkit: bump version to 0.119 and use duktape Adam Duskett
2021-07-21 21:45 ` [Buildroot] [PATCH v2 2/4] package/polkit/S50polkit: new file Adam Duskett
2021-08-05  9:46   ` Peter Korsgaard
2021-07-21 21:45 ` [Buildroot] [PATCH v2 3/4] support/testing: add polkit tests Adam Duskett
2021-07-21 21:45 ` [Buildroot] [PATCH v2 4/4] package/spidermonkey: drop package Adam Duskett
2021-07-24 21:30 ` Thomas Petazzoni [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210724233029.0b6e4d2f@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=aduskett@gmail.com \
    --cc=buildroot@buildroot.org \
    --cc=giulio.benetti@benettiengineering.com \
    --cc=marek.belisko@open-nandra.com \
    --cc=maxime.hadjinlian@gmail.com \
    --cc=nolange79@gmail.com \
    --cc=yann.morin.1998@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.