From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guile 2.0 in make-bootstrap.scm
Date: Wed, 06 Jan 2021 12:01:55 +0100 [thread overview]
Message-ID: <87mtxm5nx8.fsf@gnu.org> (raw)
In-Reply-To: <87zh1mqw10.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 06 Jan 2021 10:01:15 +0100")
Ludovic Courtès writes:
Hello Ludo!
>
> While uploading the powerpc64le-linux tarballs, I noticed they use Guile
> 2.0, which reminded me of eef44fea17a735d2f4048a747d16af478d4b9dbc:
>
> Revert "gnu: guile-static-stripped: Update to 2.2."
>
> As discussed on IRC, keeping bootstrap Guile on 2.0 simplifies adding new
> architectures and removes the need for parameterizing
> gnu/packages/bootstrap.scm.
>
> This reverts commit 2acfe022a740f79b593348cc6362cc4ee8f33bb4.
>
> * gnu/packages/make-bootstrap.scm (%guile-static): Revert to guile-2.0. Retain
> build recipe.
> * gnu/packages/patches/guile-relocatable.patch: Update for Guile 2.0.14.
>
> Do you remember the reason for this change?
I remember we hesitated gratuitously updating the %bootstrap-guile seed
(to 2.2) and decided to try to "make it work without updating the guile
seed".
I am not 100% sure, we'd have to look up the IRC discussions.
> What’s surprising is that
> <https://ftp.gnu.org/gnu/guix/bootstrap/i686-linux/20190815> does use
> 2.2.
Oh, that's weird. Well, we used gule-2.2 until almost the very last
moment, I remember. I am cc'ing Timothy, as he helped make the
guile-2.0 bootstrap possible (gash compatibility and such).
Greetings,
Janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2021-01-06 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 9:01 Guile 2.0 in make-bootstrap.scm Ludovic Courtès
2021-01-06 9:04 ` Efraim Flashner
2021-01-06 11:01 ` Jan Nieuwenhuizen [this message]
2021-01-08 17:14 ` Timothy Sample
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=87mtxm5nx8.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).