2009/11/30 Peter Stuge <[email protected]> > > USE CATALYST! > > To do this you will create stage2, stage3 and stage4 spec files > (maybe also stage1, I'm not sure on that) for catalyst. It can > produce exactly what you want. > > Fine, I believe this would be controlled by USE flags for stage2 and > up. > > Please just start playing with the catalyst examples. I hope you will > quickly learn what they produce. >
I already looked a lot into Catalyst but some points doesn't fit to my plans : - I have to use a profile if I want to specify things (for instance ports version) for base stage. I really don't want to build a profile because they're hard to maintain in a wide use scheme, and because that's overkill. - Catatalyst seems to build by substraction (I mean on livecd, it builds from a stage3, then unmerges and removes things). I want to build with additive steps (from nothing). - I want to be able to just emerge one new port or update one on a target, and with Catalyst I cant. I must rebuild all (yeah, cache is there but...), and I really need to build just one port on some cases. That's why I thought about a "build" directory built from my host with crossdev. Then I use this build env to build my target with gcc/libc I want. If I have to build just one port, I can use my build env for this target again. Since I choose what to build from nothing, I don't have to use profile to define what I put in my target or build. I don't break system by removing things. My build standard "make.conf" serves as usual, I have nothing more than a crossdev, a make.conf filling, and some emerge to a given root. That's what I want, but I don't know how to achieve this. If Catalyst can offer me this control, I would be glad to use it. -- 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
