From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Timothy Sample <samplet@ngyro.com>,
Efraim Flashner <efraim@flashner.co.il>
Cc: 39655-done@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#39655: [PATCH core-updates] doc: Add 'Scheme-only Bootstrap' node.
Date: Fri, 22 May 2020 16:20:11 +0200 [thread overview]
Message-ID: <874ks8aw6c.fsf@gnu.org> (raw)
In-Reply-To: <878shpku3n.fsf@ngyro.com> (Timothy Sample's message of "Mon, 18 May 2020 13:53:32 -0400")
Hello!
Timothy Sample writes:
>> +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?
Good question -- I've added this
compiler: GNU Mes and GNU Guile@footnote{Not shown in this graph are the
static binaries for @file{bash}, @code{tar}, and @code{xz} that are used
to get Guile running.}.
Efraim Flashner writes:
> > GNU Sed will also ship as gzipped tarballs again, as alternative to the
> > hard to bootstrap @code{xz}-compression), this set of added packages can
> > hopefully be reduced again.
> I have to ask since we're talking about bootstrapability; is it actually
> not bootstrappable or is it just harder/more complex? (The question is
> more about the wording than about the logistics of it.)
Good question, changed it to "hard to bootstrap", like so
GNU Sed will also ship as gzipped tarballs again, as alternative to the
hard to bootstrap @code{xz}-compression), this set of added packages can
hopefully be reduced again.
Thanks for your input, pushed to master!
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
prev parent reply other threads:[~2020-05-22 14:21 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
2020-05-22 14:20 ` Jan Nieuwenhuizen [this message]
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=874ks8aw6c.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=39655-done@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
--cc=ludo@gnu.org \
--cc=samplet@ngyro.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 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.