From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix Day: Notes frome the Bootstrap session
Date: Wed, 10 Feb 2021 22:59:07 +0100 [thread overview]
Message-ID: <878s7v37pw.fsf@gnu.org> (raw)
In-Reply-To: <87y2fxr6w5.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 09 Feb 2021 09:18:34 +0100")
Hi!
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> Attached the notes from the "Bootstrap what's next" session yesterday.
Thanks for sharing!
> - Making the guix build system code less dependent on Guile and more
> dependent on MES
Not necessarily more dependent on Mes :-), but rather portable between
the two.
On this topic, one action item we identified was to try and see what it
would take to run (guix build gnu-build-system) and the modules it
depends on on Mes. If we can run that on Mes during early bootstrap
(before Guile is built), then that’s a step towards removing the big
‘%bootstrap-guile’ binary seed.
These modules require some Guilish module support as well as a bunch of
(ice-9 *) and (srfi *) modules. Perhaps with some tricks such as
autoloads, we can reduce the number of modules actually needed.
Another option is to write a simplified but compatible subset of (guix
build gnu-build-system) specifically for use during early bootstrap.
At any rate, the first step is to try to feed that code to Mes and see
what happens. :-)
If you’ve always wanted to join the bootstrapping movement, now’s your
opportunity!
Ludo’.
next prev parent reply other threads:[~2021-02-10 21:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 8:18 Guix Day: Notes frome the Bootstrap session Jan Nieuwenhuizen
2021-02-10 21:59 ` Ludovic Courtès [this message]
2021-02-13 9:40 ` Jan Nieuwenhuizen
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=878s7v37pw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=janneke@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 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.