From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Replacing polkit by polkit-duktape on core-updates-frozen ?
Date: Thu, 11 Nov 2021 13:23:37 -0500 [thread overview]
Message-ID: <87k0hetuty.fsf@gmail.com> (raw)
Hello Guix!
I've finally merged the core-updates-frozen-batched-changes to
core-updates-frozen. One of the changes it brought is an updated
(non-grafted) polkit; this polkit now depends on mozjs@78 which itself
depends on rust.
Unfortunately, our rust bootstrap doesn't currently build everywhere;
progress is being made in mrustc to improve the situation as we speak
[0], but in the meantime this rust-dependent polkit will cause problems
on non-x86_64 architectures (it is needed by GTK/GNOME through elogind).
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.
What do you think?
[0] https://github.com/thepowersgang/mrustc/issues/78#issuecomment-966470873
[1] https://gitlab.freedesktop.org/polkit/polkit/-/merge_requests/35
next reply other threads:[~2021-11-11 18:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 18:23 Maxim Cournoyer [this message]
2021-11-11 23:30 ` Replacing polkit by polkit-duktape on core-updates-frozen ? Thiago Jung Bauermann
2021-11-17 11:08 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k0hetuty.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).