From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2F8E61381F4 for ; Fri, 17 Aug 2012 20:12:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8D0DCE07D5; Fri, 17 Aug 2012 20:11:50 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 37CA3E06F7 for ; Fri, 17 Aug 2012 20:10:59 +0000 (UTC) Received: from [192.168.26.5] (ip98-164-193-252.oc.oc.cox.net [98.164.193.252]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 57ADE1B4001 for ; Fri, 17 Aug 2012 20:10:58 +0000 (UTC) Message-ID: <502EA550.3090908@gentoo.org> Date: Fri, 17 Aug 2012 13:10:56 -0700 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:14.0) Gecko/20120802 Thunderbird/14.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] remove system set? References: <20120815125832.39c72a82@pomiocik.lan> <20120815110757.GV10705@gentoo.org> <20120815114153.GX10705@gentoo.org> <20120815120131.GY10705@gentoo.org> <20120815140413.GA10705@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: e1cb2ee6-deb5-4ffb-89f4-2319fb1d546d X-Archives-Hash: 046e1d75d57693e64fa80a5ce00b3b0b On 08/16/2012 08:26 PM, Michael Mol wrote: > Ideally, you'd want as narrow a bootstrapping channel as possible. > Assuming things start off statically linked, what's the sequence for > going from an empty chroot to stage 1, 2, 3...? What are the starting > conditions? We use sys-apps/catalyst, which builds stage1 in a new $ROOT by simply extracting a seed stage3 and calling $PORTDIR/scripts/booststrap.sh. The stage1 is pretty minimal, but it's enough to generate a new stage3 by simply calling emerge -e @system (you can skip stage2 step entirely). The stage2 step is just used to rebuild some essential packages for a more specialized CHOST, so it's only needed when your stage1 has a generic CHOST and you want to build a stage3 with a more specialized CHOST. -- Thanks, Zac