From: "Ludovic Courtès" <ludo@gnu.org>
To: Thiago Jung Bauermann <bauermann@kolabnow.com>
Cc: guix-devel <guix-devel@gnu.org>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Replacing polkit by polkit-duktape on core-updates-frozen ?
Date: Wed, 17 Nov 2021 12:08:24 +0100 [thread overview]
Message-ID: <87v90rxcnr.fsf@gnu.org> (raw)
In-Reply-To: <2505829.NYjHvEFHQz@popigai> (Thiago Jung Bauermann's message of "Thu, 11 Nov 2021 20:30:06 -0300")
Hi,
Thiago Jung Bauermann <bauermann@kolabnow.com> skribis:
> Em quinta-feira, 11 de novembro de 2021, às 15:23:37 -03, Maxim Cournoyer
> escreveu:
>> Hello Guix!
>>
>> I've finally merged the core-updates-frozen-batched-changes to
>> core-updates-frozen.
>
> Hooray!
>
>> One thing we could do in the meantime is to replace our polkit package
>> with polkit-duktape, which uses an (unmerged) patch to build polkit
>> against duktape rather than mozjs [1]. The patch seems to have garnered
>> some attention recently. This would enable to build GTK and parts of
>> GNOME without rust, I believe.
>
> I’d suggest replacing polkit with polkit-duktape only for non-x86_64
> architectures. What do you think?¨
Yes, that seems like the most reasonable option.
Thanks, Maxim!
Ludo’.
next prev parent reply other threads:[~2021-11-17 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 18:23 Replacing polkit by polkit-duktape on core-updates-frozen ? Maxim Cournoyer
2021-11-11 23:30 ` Thiago Jung Bauermann
2021-11-17 11:08 ` Ludovic Courtès [this message]
2021-11-22 3:35 ` Maxim Cournoyer
2021-11-22 13:30 ` Ludovic Courtès
2021-11-22 20:26 ` Maxim Cournoyer
2021-11-22 20:41 ` Maxim Cournoyer
2021-11-23 17:18 ` Ludovic Courtès
2021-11-23 20:34 ` Thiago Jung Bauermann
2021-11-24 4:11 ` Maxim Cournoyer
2021-11-24 4:02 ` Maxim Cournoyer
2021-11-24 8:42 ` Josselin Poiret via Development of GNU Guix and the GNU System distribution.
2021-11-24 14:42 ` Maxim Cournoyer
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=87v90rxcnr.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bauermann@kolabnow.com \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.