2009/12/2 Peter Stuge <[email protected]> > > Agree! No problem. Sorry for being a bit harsh. >
Thanks a lot for taking time answering on each subject I needed help for. But above it all, this answer is the most clear and understanding. > > > 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. > > Why is this important in intermediate steps? > Because I'll need some targets to run against a specific version glibc. I don't really know how to do that, but I guess I must compile target with correct target gcc/glibc. Then, I'll have to build some bin packages for just one or two port for this target, so I guess I have to preciously keep my build envs. > > Well, as I mentioned before, it is certainly possible for you to add > a kind of stage5, either using catalyst, or just with a single tar > command. This final step would be run after the stage4 and every > single file that you want to include in your final tarball would be > explicitly named there. > That's quite a good idea. I'll think about it. > > It depends on if you have a strict requirement on the process, or on > the final result. If the final result is the important thing, then > catalyst can certainly be of help even though the internal process > with several stages does not work like you describe. > That really helps. It's the good question. As I'm not alone to decide, I'll have to ask. -- 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
