From: Sage Gerard <sage@sagegerard.com>
To: guix-devel@gnu.org
Subject: Please explain these fundamental terms to me?
Date: Fri, 24 Sep 2021 18:35:20 +0000 [thread overview]
Message-ID: <1d5982ae-2cda-5661-898a-e015c7f320a1@sagegerard.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
Hello!
I'm confused about fundamental definitions from the manual.
> Possibly one of the most harmless, but certainly by far the biggest binary seed that all software distributions inject are the so [called] bootstrap binary seed. Bootstrap binaries are the initial binary seeds that are used to start building the distribution. -- https://www.gnu.org/software/mes/manual/html_node/Bootstrappable-Builds.html
This definition of bootstrap binary seeds confused me because
- "Binary seed" itself is not defined. After some searching, my understanding is that this is a verified binary you inject among source code to produce more software. Is that correct?
- it switches from singular to plural form. "The biggest binary seed is the bootstrap binary seed", followed by "Bootstrap binaries are the initial binary seeds." How do these sentences reconcile?
Also, in reading section 1.4 I didn't come away knowing what a full source bootstrap even is. Does that mean you reproduce the hex0 binary, and then use progressive stages to eventually reproduce the source code for a version of Guix? Or does it mean that you reproduce an exact disk image for an OS for the same CPU architecture as the hex program, with a copy of the Guix source ready to go on that system?
[-- Attachment #2: Type: text/html, Size: 1830 bytes --]
next reply other threads:[~2021-09-24 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 18:35 Sage Gerard [this message]
2021-09-25 12:32 ` Please explain these fundamental terms to me? Ekaitz Zarraga
2021-09-25 12:34 ` Ekaitz Zarraga
-- strict thread matches above, loose matches on Subject: below --
2021-09-24 18:36 Sage Gerard
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=1d5982ae-2cda-5661-898a-e015c7f320a1@sagegerard.com \
--to=sage@sagegerard.com \
--cc=guix-devel@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).