From: "Ludovic Courtès" <ludo@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: 39655@debbugs.gnu.org
Subject: [bug#39655] [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node.
Date: Wed, 19 Feb 2020 16:58:12 +0100 [thread overview]
Message-ID: <87eeuqmuwb.fsf@gnu.org> (raw)
In-Reply-To: <20200218124411.20400-1-janneke@gnu.org> (Jan Nieuwenhuizen's message of "Tue, 18 Feb 2020 13:44:11 +0100")
Hi!
Jan Nieuwenhuizen <janneke@gnu.org> skribis:
> * doc/guix.texi (@detailmenu): Add Bootstrapping menu.
> (Scheme-only Bootstrap): New node.
> * doc/images/gcc-core-mesboot0-scheme-only-graph.dot: New image.
> * doc/local.mk (DOT_FILES): Add it.
Great! I wonder if we need a new section though. Do you think we could
just keep it all in a single bootstrapping section that would describe
the current state of affairs, possibly with a “Bootstrapping History”
section or similar that would describe the milestones that got us there?
In fact, part of what you write here could very much go straight to such
a “History” section. I think the terms “Full Source Bootstrap”,
“Scheme-Only Bootstrap”, etc. should only appear there, for clarity.
That way, the main bootstrapping section would simply describe the
current status in a standalone fashion.
Does that make sense?
> +The next step that Guix has taken towards a Full Source Bootstrap is to
> +replace the shell and all its utilities with implementations in Guile
> +Scheme. Gash (@pxref{Gash,,, gash, The Gash manual}) is a
> +POSIX-compatible shell that replaces Bash, and it comes with Gash Utils
> +which has minimalist replacements for Awk, the GNU Core Utilities, Grep,
> +Gzip, Sed, and Tar. The rest of the bootstrap binary seeds that were
> +removed are now built from source by adding a new set of
> +@c
> +packages@footnote{@c
> +gash-boot,
> +gash-utils-boot,
> +%bootstrap-mes-rewired,
> +gzip-mesboot,
I wouldn’t list them all here because (1) it’s hard to understand what
these names refer to, unless reading commencement.scm is your favorite
hobby ;-), and (2) it’s bound to become outdated.
WDYT?
> +As Gash and Gash Utils mature, and GNU packages become more
> +bootstrappable (e.g., new releases of GNU Sed will also ship in
> +@code{tar.gz} format), this set of added packages can hopefully be
> +reduced again.
> +
> +@c ./pre-inst-env guix graph -e '(@@ (gnu packages commencement) gcc-core-mesboot0)' | sed -re 's,((bootstrap-mescc-tools|bootstrap-mes|guile-bootstrap).*shape =) box,\1 ellipse,' > doc/images/gcc-core-mesboot0-scheme-only-graph.dot
> +@image{images/gcc-core-mesboot0-scheme-only-graph,6in,,Dependency graph of gcc-core-mesboot0}
It would be nice to have a couple of lines commenting the graph, like:
The graph below shows the resulting dependency graph. At its root
there’s X and at the top there’s Y, etc.
Thank you, and apologies for suggesting more work! :-)
Ludo’.
next prev parent reply other threads:[~2020-02-19 15:59 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 [this message]
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
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
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=87eeuqmuwb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=39655@debbugs.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 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).