From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1ND0V8-0003kF-VI for garchives@archives.gentoo.org; Tue, 24 Nov 2009 18:52:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4BC33E0782; Tue, 24 Nov 2009 18:52:12 +0000 (UTC) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by pigeon.gentoo.org (Postfix) with ESMTP id D667EE0782 for ; Tue, 24 Nov 2009 18:52:11 +0000 (UTC) Received: by fxm7 with SMTP id 7so7191069fxm.29 for ; Tue, 24 Nov 2009 10:52:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=AyFQ/IX3tp5ag3PjqllsZPg/OkwiZ2utjqz1H9WQVqI=; b=qj+3zuamGV6viCWL90vS7MBeWuYE/dwCgjCDuOT8ptRVaOVvMkDCtqs4mH7a1dqgIw O6sSa9nPz5G52GEZB5CDVJwuPk7PpYCfYDCEc/Uohz7ocuJmxERXvgyss3VVq7CICC3B Y4PgNwSDO5/x0Jm9/VPEyZbeHdZZhTOt0zyJ8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=a0+PPLDK5noHT4AkN+jpYb1/TKVdCt5qL8P0RipfW8Dz6Ao0fEUWSlaFy2VSMG0el6 z9liLw2KmLYsx2h9CElmOzSnfWNi2OsVMdnK55STYSZpv+73mQh0rbGeAHQ7VsgM4dv0 TW7gPihRsZHao8tXcT4cvu7I1t4TV8GWw0gRI= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-catalyst@lists.gentoo.org Reply-to: gentoo-catalyst@lists.gentoo.org MIME-Version: 1.0 Received: by 10.223.73.20 with SMTP id o20mr980336faj.71.1259088731099; Tue, 24 Nov 2009 10:52:11 -0800 (PST) In-Reply-To: <20091124173702.9617.qmail@stuge.se> References: <166af1cf0911240610j52fdda71vd082ab515f39d33a@mail.gmail.com> <20091124173702.9617.qmail@stuge.se> From: Shinkan Date: Tue, 24 Nov 2009 19:51:51 +0100 Message-ID: <166af1cf0911241051p1f6c13cbu471824822035c8b9@mail.gmail.com> Subject: Re: [gentoo-catalyst] Sort of Build Platform To: gentoo-catalyst@lists.gentoo.org Content-Type: multipart/alternative; boundary=0015174a047a8ed2ba0479227013 X-Archives-Salt: d087737e-3099-47e1-b3eb-f95297b3e990 X-Archives-Hash: 7d1c374761a4dc97dcb045b2a502a301 --0015174a047a8ed2ba0479227013 Content-Type: text/plain; charset=UTF-8 Thank you for your answer. By inspecting catalyst examples specs, especially stage4 one, I figured that catalyst could do the job. Right now I proceed by "cross-emerging" from a Gentoo host to a target dir with emerge's --root and --config-dir opts. With that, I can start with an empty target dir, and emerge into it baselayout, bash and glibc. That's all I need for now. Then I cross compile needed kernel to my target dir following Gentoo cross-dev guide : http://www.gentoo.org/proj/en/base/embedded/cross-development.xml#doc_chap6 That's what I need. But that's all hand-crafted scripts to always build the same things. Plus, I will have to make my target dir a LiveCD just after, so I'll have to script more. I thought Catalyst could do the exact same thing with a more Gentoo-ish way and sort-of cache settings. But I'm still not sure. Plus I don't get the "stage"-related thing in spec. I read FAQ and get it a little more. Here are the 2 crucial points that I don't want to evade : 1) I do not want to build with a "deploy base Gentoo system, then remove" strategy (won't this break things ?). I really want to start from nothing, or from a almost-empty root dir/tar I define. Because I want my target system to be a "oneshot" system. It will not use portage, or gcc. It will just run applications. 2) I do not want my target system to bootstrap itselfs by compilating its binaries. I want my host system to build target things. Because of 1) reasons. Can catalyst still do the job ? Why exactly should I make a profile ? 2009/11/24 Peter Stuge > Shinkan wrote: > > - I want to build barely-usable minimal systems that I call > > "guests" from my host. Guests would have to be setup on target > > machines using fdisk and tar only, or put on a Live{CD,DVD,USB}. > .. > > Did I have to use Catalyst ? How can I do this if it's the clean > > way ? > > You can certainly do it with a catalyst stage4 spec file. You'll also > need to prepare a kernel configuration for the guests, and reference > that in the spec file. You'll also spend some time on filling the > spec file with packages, files and directories that should be > unmerged and simply rm:ed from the final build. > > To make changes (like add another package to a guest) you would run > catalyst again. It starts over, but keeps a cache of binpkgs that > have been built so it runs well under an hour even on oldish systems. > > This is how I make custom distributions for customers. > > Since the guests will be very different from a standard Gentoo system > it may also be worthwhile for you to create a new, custom, profile > for the guests. > > > //Peter > > -- Pierre. "Sometimes when I'm talking, my words can't keep up with my thoughts. I wonder why we think faster than we speak. Probably so we can think twice." - Bill Watterson --0015174a047a8ed2ba0479227013 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Thank you for your answer.
By inspecting catalyst examples specs, especi= ally stage4 one, I figured that catalyst could do the job.

Right now= I proceed by "cross-emerging" from a Gentoo host to a target dir= with emerge's --root and --config-dir opts.
With that, I can start with an empty target dir, and emerge into it baselay= out, bash and glibc. That's all I need for now.
Then I cross compile= needed kernel to my target dir following Gentoo cross-dev guide : http://www.gentoo.org/proj/en/base/embedded/cross-development.xml#doc= _chap6

That's what I need. But that's all hand-crafted scripts to alwa= ys build the same things.
Plus, I will have to make my target dir a Live= CD just after, so I'll have to script more.

I thought Catalyst c= ould do the exact same thing with a more Gentoo-ish way and sort-of cache s= ettings.
But I'm still not sure. Plus I don't get the "stage"-rela= ted thing in spec. I read FAQ and get it a little more.

Here are th= e 2 crucial points that I don't want to evade :
1) I do not want to = build with a "deploy base Gentoo system, then remove" strategy (w= on't this break things ?). I really want to start from nothing, or from= a almost-empty root dir/tar I define. Because I want my target system to b= e a "oneshot" system. It will not use portage, or gcc. It will ju= st run applications.
2) I do not want my target system to bootstrap itselfs by compilating its b= inaries. I want my host system to build target things. Because of 1) reason= s.

Can catalyst still do the job ?
Why exactly should I make a pr= ofile ?

2009/11/24 Peter Stuge <= ;peter@stuge.se>
Shinkan wrote:
> - I want to build barely-usable minimal systems that I call
> "guests" from my host. Guests would have to be setup on targ= et
> machines using fdisk and tar only, or put on a Live{CD,DVD,USB}.
..
> Did I have to use Catalyst ? How can I do this if it= 's the clean
> way ?

You can certainly do it with a catalyst stage4 spec file. You'll = also
need to prepare a kernel configuration for the guests, and reference
that in the spec file. You'll also spend some time on filling the
spec file with packages, files and directories that should be
unmerged and simply rm:ed from the final build.

To make changes (like add another package to a guest) you would run
catalyst again. It starts over, but keeps a cache of binpkgs that
have been built so it runs well under an hour even on oldish systems.

This is how I make custom distributions for customers.

Since the guests will be very different from a standard Gentoo system
it may also be worthwhile for you to create a new, custom, profile
for the guests.


//Peter




--
Pierre.
"= ;Sometimes when I'm talking, my words can't keep up with my thought= s. I wonder why we think faster than we speak. Probably so we can think twi= ce." - Bill Watterson
--0015174a047a8ed2ba0479227013--