unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
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: Sat, 27 Nov 2021 23:43:41 +0100	[thread overview]
Message-ID: <87sfvhnrm2.fsf@elephly.net> (raw)
In-Reply-To: <8735nh8bvw.fsf@inria.fr>


Ludovic Courtès <ludo@gnu.org> writes:

> As you may know, librsvg 2.50 on ‘core-updates-frozen’ depends 
> on Rust.
> However mrustc, which we use to build the first Rust compiler, 
> currently
> only works on x86_64.  This means that ~28% of the packages on
> ‘core-updates-frozen’ are x86_64-only (vs. ~15% on ‘master’).
>
> Among these, the most problematic missing packages are desktop
> environments: Xfce, GNOME, etc.  So far our “pledge”, encoded in
> ‘etc/release-manifest.scm’, was that all the desktop 
> environments would
> be available on x86_64 and i686, so that one could install Guix 
> System
> just the same way on both.  Currently this is no longer possible 
> on
> ‘core-updates-frozen’, and I think that’s a problem.
>
> The patch below does something unorthodox: it reintroduces 
> librsvg 2.40
> (written in C) and uses it selectively so we can have a desktop
> environment with Xfce on i686.  It’s not enough to get GDM 
> though;
> there’s a couple of GNOME packages that depend on librsvg and I 
> haven’t
> checked whether they work with the old librsvg.

There is also the unpleasant option to introduce a rust binary for 
architectures other than x86_64, because we can’t bootstrap it 
there.  It should be noted that this would not be unprecedented. 
We have bootstrap binaries for some compilers such as Free Pascal 
or GHC.

Adding an old version of librsvg is not obviously the better 
option.

-- 
Ricardo


  reply	other threads:[~2021-11-27 22:47 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 [this message]
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
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=87sfvhnrm2.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).