public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] [PATCH] doc/HOWTO.txt: Fix stage descriptions
Date: Thu, 19 Dec 2013 21:51:59 -0500	[thread overview]
Message-ID: <52B3B0CF.2030404@gentoo.org> (raw)
In-Reply-To: <52B39E5A.5010006@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/19/2013 08:33 PM, Rick "Zero_Chaos" Farina wrote:
> On 12/19/2013 06:48 PM, W. Trevor King wrote:
>> From: "W. Trevor King" <wking@tremily.us>
> 
>> Thanks to Zero_Chaos for clarification on #gentoo-releng.
>> ---
>>  doc/HOWTO.txt | 10 ++++++----
>>  1 file changed, 6 insertions(+), 4 deletions(-)
> 
>> diff --git a/doc/HOWTO.txt b/doc/HOWTO.txt
>> index 5717f80..90593d7 100644
>> --- a/doc/HOWTO.txt
>> +++ b/doc/HOWTO.txt
>> @@ -137,10 +137,12 @@ 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.
>> +   (a profile's `packages.build` toolchain built with external seed
>> +   tools).
>> +2. Stage1 + bootstrapped Portage (`/usr/portage/scripts/bootstrap.sh`).
> NACK- this isn't accurate. stage2 runs /usr/portage/scripts/bootstrap.sh
> not stage1
> 
NACK NACK, I can't read properly.  Since I was confused wking has agreed
on irc to a new format entirely to avoid people as stupid as me.

Waiting on V2
- -Zero
> 
>> +3. Stage2 + base system compiled (the base `@system` built with stage2
>> +   tools).
>> +4. Stage3 + non-base packages (`@world`).
> 
>>  For more details on the differences between the stages, look at the
>>  target helper scripts (e.g. `targets/stage1/*.sh`).
> 
> 
> 
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSs7DPAAoJEKXdFCfdEflKJyoP/3k4f6SsQF2Rk15rzsWlvrNX
dxMen6rBZqNT5BiEcgZngJzDPDdMYqCfYBis3qFVtTVQX+QIbEXPzJJ2kWgSpPQv
br0kVvUvhrzSEM8o0r4ohVkLNq5PfsAQqz4Zcbbs00Y05HX/3cF24HxrHzs6UyZA
AVibaTkFf4iZmDClCg9mhjTMRRJ5G4N1m0cuiipLp9Q71XQLS9wlZKLdjsxZx7w9
8coJpfkUj53SWJ7kG0Tvt00XSMioYmKI817VDQFR8QAuKWIEA0e2vFjm/CTMGlDS
S7NOAHE/TUe83iheqKYnVUluIjA8cRxjjZ9ZCmkSZS+Ti+uSvxPJ+h94803QwKnw
Fri6vk1W7d3+tIUtSSYVM7SV0G+LKjbIPsX9H77XUkRQTYMwHPTiO8DqCQXSVNbT
7R4eWWF5aWhX0sIUHyqZWK+bp8GIQ3mujLHJ7kJuuOVOL7Z7zcXlKn2Y2whQzLXb
sV8/bN3UIlq7nYvFWruUc+5bAtRKG/1SsiDuJIrawKQ5c67YG2tsDnNVVjYG/flQ
T6QHXgxvCwPPUESQjUK1wYUeuc1wRE+7JnAeILCfsyyy06LeOzc2FyzKx/osOX/o
45JjU+qiQ4VRPQTEzblhXjXGJ9KJ5sgVBB4a9sXUXGTbxMsJbbw5iShjf7ud7NRc
zhhwkW/UfQbuQbrt2Q87
=IOuA
-----END PGP SIGNATURE-----


  reply	other threads:[~2013-12-20  2:50 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 [this message]
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
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=52B3B0CF.2030404@gentoo.org \
    --to=zerochaos@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