Re: [gentoo-catalyst] Sort of Build Platform

[Peter Stuge <peter@stuge.se>]

Pierre,

Please don't top-post.


Shinkan wrote:
> I thought Catalyst could do the exact same thing with a more
> Gentoo-ish way and sort-of cache settings.

Yes, that is also a good summary of what I wrote.


> But I'm still not sure.

Be sure.


> 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
..
> 2) I do not want my target system to bootstrap itselfs
..
> Can catalyst still do the job ?

For the fourth time: catalyst does what you want.

It creates a stage tarball according to instructions in a spec file.
It uses emerge to build and install all packages in the stage. It
saves binary packages of everything that has been built to save time
if you want to make changes and run catalyst again. You specify how
you want the tarball (or livecd) to be produced, by adding
information to the spec file.


> Why exactly should I make a profile ?

Because your target or guest system will be sufficiently different
from what the Gentoo profiles are intended for.


In your case another idea is to create a simple script that runs
after the stage4 is completed. Then you will not unmerge, empty or rm
anything in the stage4 spec file, but use your script to create the
deployment tarball with only the specific binaries and libraries that
you want. Of course avoiding the script has the big advantage that
you can encapsulate everything in a spec file and have catalyst
generate the final product, but it will have a long list with lots of
files that should _not_ be included. Having your own profile helps in
shortening that list too.


//Peter