From: Timothy Sample <samplet@ngyro.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 39655@debbugs.gnu.org
Subject: [bug#39655] [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node.
Date: Mon, 18 May 2020 13:53:32 -0400 [thread overview]
Message-ID: <878shpku3n.fsf@ngyro.com> (raw)
In-Reply-To: <87367yhgva.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Sun, 17 May 2020 14:43:05 +0200")
Hi janneke,
Overall it is very good! I only have a one small suggestion.
Jan Nieuwenhuizen <janneke@gnu.org> writes:
> [...]
>
>>> +As Gash and Gash Utils mature, and GNU packages become more
>
> @Timothy: this is possibly touching very lightly on what Gash has
> brought us; do you want to share some more here?
Honestly I think this says enough for now. I have most of the code in
place so that Gash can build nearly anything. (In particular, Awk is
nearly complete with respect to POSIX.) It will take a while to clean
it up, but we can refresh this part when the new code lands. :)
> [...]
>
> +The only significant binary bootstrap seeds that remain@footnote{
> +Ignoring the 68KB @code{mescc-tools}; that will be removed later,
> +together with @code{mes}.} are a Scheme intepreter and a Scheme
> +compiler: GNU Mes and GNU Guile.
Is it too confusing to mention the Bash, Tar, and XZ binaries used to
get Guile up and running? IIRC, there are a few packages whose sources
are still patched via “bootstrap-origin”, too. I understand that those
binaries are really insignificant, but maybe someone new to this whole
thing would be surprised to discover “secret” bootstrap binaries.
Perhaps their role in unpacking Guile could be put in the footnote with
messcc-tools. WDYT?
-- Tim
next prev parent reply other threads:[~2020-05-18 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 12:44 [bug#39655] [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node Jan Nieuwenhuizen
2020-02-19 15:58 ` Ludovic Courtès
2020-05-17 12:43 ` Jan Nieuwenhuizen
2020-05-17 12:51 ` Jan Nieuwenhuizen
2020-05-17 22:05 ` Nicolas Goaziou
2020-05-18 5:27 ` Jan Nieuwenhuizen
2020-05-18 6:57 ` Efraim Flashner
2020-05-18 7:37 ` Jan Nieuwenhuizen
2020-05-18 7:37 ` Nicolas Goaziou
2020-05-18 7:50 ` Jan Nieuwenhuizen
2020-05-18 17:53 ` Timothy Sample [this message]
2020-05-22 14:20 ` bug#39655: " 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=878shpku3n.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=39655@debbugs.gnu.org \
--cc=janneke@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 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.