Shinkan wrote:
> Just one simple question :
> Let's say I want to use a base official gentoo stage3 to build a
> stage4 with catalyst.
> Let's say I wrote my own profile, which defines a very very minimal
> system with no gcc, no portage, ..., and that I use this profile
> for stage4.

This is an error. It may work, but if you are going to use a custom
profile you should create all stages where profile differences will
result in different contents than what release engineering produces.
This goes at least back to stage2 and maybe even stage1.


> If I use catalyst stage4 spec file type, which takes a stage3 as a
> seed, would my stage4 contains everything from stage3 (that I don't
> explicitely remove),

Yes.


> or would my stage4 be built from scratch by stage3 (and contains
> just system ports my stage4 profile specified) ?

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.


> The same question goes for livecd.

The same answer.


> Would my final livecd contain stage3 or livecd-stage1 build tools
> if I define a minimal system profile for livecd-stage2 ?

Every catalyst target uses a source tarball, and the created target
will contain everything in that source tarball which you do not
remove.


This is why it is smart to create your own profile and build your own
early stages. That way your early stages will never include any of
the packages that are good for standard systems but which you do not
want in your final targets.


//Peter