From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH v3] doc/HOWTO.txt: Fix stage descriptions
Date: Fri, 20 Dec 2013 16:02:39 -0800 [thread overview]
Message-ID: <1387584159.3897.228.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <3614940041744d107ceff3e460e8549204c9b498.1387512969.git.wking@tremily.us>
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
On Thu, 2013-12-19 at 20:17 -0800, W. Trevor King wrote:
> From: "W. Trevor King" <wking@tremily.us>
>
> Thanks to Zero_Chaos and dwfreed for clarification on #gentoo-releng.
> ---
> Changes from v2:
> * Don't mention "Portage" in stage1 → stage2 to avoid confusion
> between Porage-the-software and Portage-the-ebuild-tree.
>
> doc/HOWTO.txt | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
> index 5717f80..20427cf 100644
> --- a/doc/HOWTO.txt
> +++ b/doc/HOWTO.txt
> @@ -136,11 +136,14 @@ compiled toolchain, which is where Gentoo's stages come in. The “base
> system” contains the necessary build tools and supporting
> infrastructure to get things going. The stages are:
>
> -1. System must be bootstrapped and the base system must be compiled
> - (a new toolchain built with external seed tools).
> -2. Stage1 + bootstrapped (a new toolchain build with stage1 tools).
> -3. Stage2 + base system compiled (the base system built with stage2 tools).
> -4. Stage3 + non-base packages.
> +[options="header",frame="topbot",grid="none"]
> +|=======================================================================================
> +| Source | Action | Result
> +| seed stage3 | Bootstrap a profile's `packages.build` toolchain | stage1
> +| stage1 | Rebuild the toolchain with the package tree's `bootstrap.sh` | stage2
> +| stage2 | Compile the base `@system` packages | stage3
> +| stage3 | Compile additional `@world` packages | stage4
> +|=======================================================================================
>
> For more details on the differences between the stages, look at the
> target helper scripts (e.g. `targets/stage1/*.sh`).
This looks good to me. I like the table showing the steps.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2013-12-21 0:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 23:48 [gentoo-catalyst] [PATCH] doc/HOWTO.txt: Fix stage descriptions W. Trevor King
2013-12-20 1:33 ` Rick "Zero_Chaos" Farina
2013-12-20 2:51 ` Rick "Zero_Chaos" Farina
2013-12-20 3:13 ` [gentoo-catalyst] [PATCH v2] " W. Trevor King
2013-12-20 4:17 ` [gentoo-catalyst] [PATCH v3] " W. Trevor King
2013-12-20 4:27 ` Rick "Zero_Chaos" Farina
2013-12-31 17:05 ` Jorge Manuel B. S. Vicetto
2013-12-21 0:02 ` Brian Dolbec [this message]
2013-12-21 4:39 ` [gentoo-catalyst] [PATCH v4] doc/HOWTO.txt: Fix stage descriptions, and add extra context W. Trevor King
2013-12-21 5:00 ` [gentoo-catalyst] [PATCH v5] " W. Trevor King
2013-12-21 5:15 ` [gentoo-catalyst] [PATCH v6] " W. Trevor King
2013-12-31 17:08 ` Jorge Manuel B. S. Vicetto
2013-12-31 17:15 ` W. Trevor King
2013-12-31 21:56 ` Rick "Zero_Chaos" Farina
2014-01-06 3:52 ` [gentoo-catalyst] " W. Trevor King
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=1387584159.3897.228.camel@big_daddy.dol-sen.ca \
--to=dolsen@gentoo.org \
--cc=gentoo-catalyst@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox