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 1NFm7L-0007Xb-Se for garchives@archives.gentoo.org; Wed, 02 Dec 2009 10:07:30 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 25055E07EE; Wed, 2 Dec 2009 10:07:24 +0000 (UTC) Received: from mail-fx0-f217.google.com (mail-fx0-f217.google.com [209.85.220.217]) by pigeon.gentoo.org (Postfix) with ESMTP id C7527E084C for ; Wed, 2 Dec 2009 10:07:23 +0000 (UTC) Received: by fxm9 with SMTP id 9so30383fxm.10 for ; Wed, 02 Dec 2009 02:07:23 -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=17ExisXDxrDhkb7saecditm6GEMSgzIiYYii/giJU0M=; b=XIInzxnW9+shPC9lSa+YvpwGRH3ahgvi8fIida0a5B519iSwVHVZ5gg4Mi29W9DIEM g1kIHVeiw3jpXLyX6JSZLcxQuzzuZvqzcJHw1xM7BLZagqN2JY1ooMLKKqngB2Lyfflz 2LRVfk317wlWlAv1dF9W/iGSA9/YX1EjsmcGI= 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=fHkMZE6uDl6SH0Xaq9JcwUOc5abj98b12GzWkforS0IYGcaqTdIVjluQFcGCmgdPP9 4P/YOptDf1Pc9lpzfEEVSStbmOtdSKEv0RcTXZhGNukhCqIgDhryFWAfmSQZTHr2CkSE lkHcg6RqCF8t/V1g9QfLaP7jB27PAhKqiXh0I= 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.14.145 with SMTP id g17mr1144714faa.51.1259748443061; Wed, 02 Dec 2009 02:07:23 -0800 (PST) In-Reply-To: <20091202094414.13781.qmail@stuge.se> References: <166af1cf0912020124o35468591y379900e7f900c9c2@mail.gmail.com> <20091202094414.13781.qmail@stuge.se> From: Shinkan Date: Wed, 2 Dec 2009 11:07:03 +0100 Message-ID: <166af1cf0912020207u7af47e10kdbb6543ab892404@mail.gmail.com> Subject: Re: [gentoo-catalyst] Catalyst stages inter-dependencies To: gentoo-catalyst@lists.gentoo.org Content-Type: multipart/alternative; boundary=00151747360a747e7e0479bc0afa X-Archives-Salt: 71f37d56-a9f1-44b5-9f59-0ab10c47e591 X-Archives-Hash: 93e69a05307a9ce0c3186526acb8548c --00151747360a747e7e0479bc0afa Content-Type: text/plain; charset=UTF-8 2009/12/2 Peter Stuge > No. If you had experimented a little with catalyst and spec files > this is one of the things that you would have discovered immediately > from the catalyst output. > Pretty fair... I experimented "a little" with catalyst. Except if a little means "more than 3 days". As I used unmerge and remove directives (as suggested by examples specs), I could not figure it out easily, sorry I have to ask, but except if I get it wrong, that mostly why mailing-lists come for : answering for more experimented users feedback. > Every catalyst target uses a source tarball, and the created target > will contain everything in that source tarball which you do not > remove. > OK so let's say I define a profile early. If I build a stage1, I'll have to use a existing stage3. Will this stage1 have stage3 files which are not removed ? No I think. But then if I want to build stage2, catalyst will be expecting stage1 to be able to build stage2 isn't it ? The point (since the begining), is that I don't want my base system to have gcc and portage. I don't want to remove them : I don't want them at all. In any stage. So I really don't get why I would have to create a profile, stage1 to stage4 ... to still remove and unmerge gcc and portage at the end ! I think I don't get clear on my aim : I want to make a build env with gcc/portage/all the build stuff. From this env I want to build a target from scratch. The target won't have build tools in it at any point. I don't want the usual Gentoo way where all stage is built by preceding one, and is composed of preceding one. I want build place and target to be clearly separated, and I don't wat to apply a "remove things" behavior to target. I try things with catalyst, I promise, including writing profile, but I don't get to my aim. And you still seems pretty sure that catalyst can do that ! -- 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 --00151747360a747e7e0479bc0afa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

2009/12/2 Peter Stuge = <peter@stuge.se>
No. If you had experimented a little with catalyst and spec files
this is one of the things that you would have discovered immediately
from the catalyst output.

Pretty fair... I experim= ented "a little" with catalyst. Except if a little means "mo= re than 3 days".
As I used unmerge and remove directives (as sugges= ted by examples specs), I could not figure it out easily, sorry I have to a= sk, but except if I get it wrong, that mostly why mailing-lists come for : = answering for more experimented users feedback.
=C2=A0
Every= catalyst target uses a source tarball, and the created target
will contain everything in that source tarball which you do not
remove.

OK so let's say I define a profile ear= ly.
If I build a stage1, I'll have to use a existing stage3.
Will= this stage1 have stage3 files which are not removed ? No I think.
But then if I want to build stage2, catalyst will be expecting stage1 to be= able to build stage2 isn't it ?
The point (since the begining), is = that I don't want my base system to have gcc and portage. I don't w= ant to remove them : I don't want them at all. In any stage.
So I really don't get why I would have to create a profile, stage1 to s= tage4 ... to still remove and unmerge gcc and portage at the end !

<= br>I think I don't get clear on my aim :
I want to make a build env = with gcc/portage/all the build stuff. From this env I want to build a targe= t from scratch.
The target won't have build tools in it at any point.
I don't wa= nt the usual Gentoo way where all stage is built by preceding one, and is c= omposed of preceding one.
I want build place and target to be clearly se= parated, and I don't wat to apply a "remove things" behavior = to target.

I try things with catalyst, I promise, including writing pr= ofile, but I don't get to my aim.
And you still seems pretty sure th= at catalyst can do that !


--
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 twic= e." - Bill Watterson
--00151747360a747e7e0479bc0afa--