From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1GPuer-0000Xw-SG for garchives@archives.gentoo.org; Wed, 20 Sep 2006 05:30:06 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.6) with SMTP id k8K5SxWJ005457; Wed, 20 Sep 2006 05:28:59 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.13.8/8.13.6) with ESMTP id k8K5OphC015520 for ; Wed, 20 Sep 2006 05:24:52 GMT Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 34ECD647A0 for ; Wed, 20 Sep 2006 05:24:51 +0000 (UTC) Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06928-08 for ; Wed, 20 Sep 2006 05:24:45 +0000 (UTC) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by smtp.gentoo.org (Postfix) with ESMTP id 76BA86457C for ; Wed, 20 Sep 2006 05:24:43 +0000 (UTC) Received: by py-out-1112.google.com with SMTP id b29so145197pya for ; Tue, 19 Sep 2006 22:24:43 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=tKhylDCQ6HdZkjh5kKbFkB1O/ALm17rs8IKIHP5RvJHBJ+Xw5mJLqI61Xn2lfslAuh/Npq4DcpZ5bGz3mF8SjfcNGQ2nEccueymSTEfbMwxINl303+mhn4QdWKXC5HaxWi1NWfg04rmoa5cWcU7piTyvzwXXdjM0i2fJ8Nzvpf0= Received: by 10.35.84.12 with SMTP id m12mr27712451pyl; Tue, 19 Sep 2006 22:24:43 -0700 (PDT) Received: by 10.35.123.16 with HTTP; Tue, 19 Sep 2006 22:24:43 -0700 (PDT) Message-ID: <92c85b0e0609192224w6ac68885i938f5685eca11097@mail.gmail.com> Date: Wed, 20 Sep 2006 07:24:43 +0200 From: "Alon Keren" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Creating a LFS system with Portage In-Reply-To: <7573e9640609191333p4a15f00bt90e0e3ca240e7c99@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <92c85b0e0609190621t52e8d65cs5e988b0fda31c2a1@mail.gmail.com> <7573e9640609191333p4a15f00bt90e0e3ca240e7c99@mail.gmail.com> X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Status: No, score=-1.884 required=5.5 tests=[AWL=0.515, BAYES_00=-2.599, DNS_FROM_RFC_ABUSE=0.2] X-Spam-Score: -1.884 X-Spam-Level: X-Archives-Salt: a79f8add-1a3b-40c2-9d7b-902146b5c4b3 X-Archives-Hash: b863b401d92b96463e41a185412bfa52 On 9/19/06, Richard Fish wrote: > On 9/19/06, Alon Keren wrote: > > My aim is to have the ability to regularly build and maintain > > completely customized Linux systems. > > This should be possible by using your own local portage tree (probably > based initially on Gentoo's tree) that you update somewhat manually > with ebuilds and eclasses as you want. Combined with pre-built binary > packages, and a 'golden' portage configuration and world file, it > should be relatively simple & quick to stage a new system. > .... > > This _is_ going to require a solid understanding of how Gentoo/Portage > works, but not necessarily how to write ebuilds/eclasses. You need to > understand what we mean by "portage tree", "world file", "use flags", > "profile", "binary packages", etc. The best way to acquire this > knowledge is to install and use Gentoo, daily, for something > significant (like your desktop!). > Yes, I realize that deep understanding of Portage would obviously be required, as will writing ebuilds (and copying some of Gentoo's). > > The ROOT variable is probably a major part of the solution, but is it > > enough? I've also found '/usr/portage/scripts/bootstrap.sh', which > > seems suspiciously relevant, but comes with little external > > documentation. > > bootstrap.sh _is_ for only rebuilding the toolchain. Probably not > what you want at all.... > It's actually what I DO want. As I've previously explained, it would give me the control I need over the system. > If Gentoo's minimal installation CD and a stage1 install doesn't work > for you, you can build your own release media with catalyst (no, it > isn't just for rebuilding the toolchain). Release media would be good, but I'd like to know how more about how Catalyst produces the toolchain. > The ROOT variable is used to install packages into a different (fex > chroot) directory. It is usually used for things like > cross-compilation environments where one wants to build binary > packages for another system, although not always. > Cross-compilation is something I would like to be able to do. >>From what I've gathered so far, it looks llike it should be possible to build a complete customized toolchain with Portage, even if it'd require some tweaking; at the center of it being the ROOT env. variable and 'bootloader.sh'. Still, I wish I could get input from someone who's actually done such a thing. Alon PS. Please CC me your replies as I'm not subscribed to messages from this list -- gentoo-user@gentoo.org mailing list