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 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.