all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Sage Gerard <sage@sagegerard.com>
Cc: guix-devel@gnu.org
Subject: Re: Please explain these fundamental terms to me?
Date: Sat, 25 Sep 2021 12:34:35 +0000	[thread overview]
Message-ID: <Jz3CaR6VIPsQHfln4BD6-ylqC8ZP3CX_Tjf_E1QWm25ckuV8iSPGCoW5M_005jJg_dRt2a2A1dFI8gbqBcdA-j_OQaMgTqN_6AOzp3EfVHw=@elenq.tech> (raw)
In-Reply-To: <aBbzBIbTJUM01lG0EuVKTyOWTgi4JfKKz6GOiyYtTBsKnv7dlinQGrDATzl2tWrH_yw09EQFH48YrdpWmXJOPtdiBkqUByU1IDwApUu5y1k=@elenq.tech>

[-- Attachment #1: Type: text/plain, Size: 2884 bytes --]

> So the software Guix release comes with coul only have source packages and be able to build everything from source, using Stage0.

So the Guix release could only have source packages and be able to build everything from source, using Stage0.

(LOL I don't know what I did in that sentence)

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, September 25th, 2021 at 2:32 PM, Ekaitz Zarraga <ekaitz@elenq.tech> wrote:

> Hi,
>
> This should be clarified in the docs. I understand your confusion.
>
> Binary seeds are all the binaries that are needed for the instalation to start. They normally include Bash, GCC and that kind of stuff. So the instalation process starts with those and uses them as tools to build all the packages needed from source.
>
> The full source bootstrap project aims to eliminate those binaries from the process. This means those programs will be built from source too.
>
> Stage0 is a big part of the full source bootstrap. It is based on several assemblers that finally are able to compile GCC (through many steps, including the compilation of a heavily patched version of TCC).
>
> So the software Guix release comes with coul only have source packages and be able to build everything from source, using Stage0.
>
> I'm not sure if this explanation is the best or if it helps, but I hope it does.
>
> If you have more questions or anything don't hesitate to ask.
>
> Best,
> Ekaitz
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, September 24th, 2021 at 8:35 PM, Sage Gerard <sage@sagegerard.com> wrote:
>
>> 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: 4062 bytes --]

  reply	other threads:[~2021-09-25 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 18:35 Please explain these fundamental terms to me? Sage Gerard
2021-09-25 12:32 ` Ekaitz Zarraga
2021-09-25 12:34   ` Ekaitz Zarraga [this message]
  -- 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='Jz3CaR6VIPsQHfln4BD6-ylqC8ZP3CX_Tjf_E1QWm25ckuV8iSPGCoW5M_005jJg_dRt2a2A1dFI8gbqBcdA-j_OQaMgTqN_6AOzp3EfVHw=@elenq.tech' \
    --to=ekaitz@elenq.tech \
    --cc=guix-devel@gnu.org \
    --cc=sage@sagegerard.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.