From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: Re: Desktops on non-x86_64 systems
Date: Sun, 28 Nov 2021 19:15:47 +0100 [thread overview]
Message-ID: <87k0gsnnvy.fsf@elephly.net> (raw)
In-Reply-To: <874k7w9nm9.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> We could try that, but IMO we first need a solution within
> days—we just
> cannot reasonably let this branch go on for longer than that.
> The
> librsvg 2.40 hack would give us Xfce (maybe GNOME?) on i686
> today.
>
> Perhaps we can address all this in several steps:
>
> 1. apply the librsvg 2.40 hack now so we can merge
> ‘core-updates-frozen’ this week for real;
>
> 2. later on, introduce some Rust binary for non-x86_64; that
> would
> lead to rebuilds only on those architectures;
>
> 3. eventually, update mrustc (and have it call gcc with -O0 to
> reduce
> its memory footprint), or use GCC-Rust instead of that’s
> viable.
>
> WDYT?
This sounds sensible. Merging core-updates-frozen does *not* mean
that it needs to be ready for release. It’s been delayed for too
long and further delays just serve to taint our morale and drain
our energy, applying fixes again and again with no end in sight.
These ongoing delays have made core-updates-frozen grow so much in
scope that we cannot afford to delay a merge any longer. Let’s
merge asap, even if that means using an older librsvg right now.
Then add rust for non-x86_64 — either by cross-building it
ourselves or getting an existing binary to restore feature parity.
Then work on a long-term solution.
--
Ricardo
next prev parent reply other threads:[~2021-11-28 18:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 22:36 Desktops on non-x86_64 systems Ludovic Courtès
2021-11-27 22:43 ` Ricardo Wurmus
2021-11-28 3:05 ` Maxim Cournoyer
2021-11-28 3:28 ` Maxim Cournoyer
2021-11-28 3:43 ` John Soo
2021-11-28 7:29 ` Tobias Platen
2021-11-28 8:57 ` Ricardo Wurmus
2021-11-28 17:49 ` Ludovic Courtès
2021-11-28 18:15 ` Ricardo Wurmus [this message]
2021-11-30 15:36 ` Maxim Cournoyer
2021-12-06 12:38 ` Ludovic Courtès
2021-12-01 4:56 ` Maxim Cournoyer
2021-12-01 17:49 ` Ludovic Courtès
2021-12-01 19:37 ` Maxim Cournoyer
2021-12-02 3:26 ` Maxim Cournoyer
2021-12-06 2:18 ` Maxim Cournoyer
2021-12-06 12:30 ` Ludovic Courtès
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=87k0gsnnvy.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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).