Eckard Brauer wrote:
My favourite target would be to Gentoo-ify a couple of servers -- means
to have a flexible build system. That in turn means to build different
types of targets (database, xen-host, app-engine, web server, etc.; I
already can do that with stage4) and to individually (1) fill that
targets with (1.a) configuration, (1.b) some custom code and data and
(2) build one or more (non-ISO9660) file system image(s) of it, which
can be sent to a LV or a storage system for use (boot) afterwards.
Where is the best place to do so, will I have to create a stage5 target
(how? -- I suspect this is the way to go) or is there a good hook in
stage4 I simply didn't see?
Possibly only loosely hitting your target, but I recently posted my
experience on using custom profiles to handle my vserver needs. In my
case I'm not eliminating gcc from my guests, and only using binpackages
as a convenience not as the only option, however, the basic principle
has worked really nicely.
As advised by someone else on the list I created subprofiles for
different types of servers and then I can enforce say certain useflags
for the nginx servers which are different to the apache servers, etc
I think I posted this on hardened, but I'm getting a bit confused which
list we are having this discussion on since it seems to be happening on
both -embedded and -hardened?
Good luck
Ed W
