Andreas wrote: > What we did here, is writing make files. Such things are handled with m4 > here. Also stuff like the > timestamp. So you'd call > make snapshot livecd_stage1 livecd_stage2 write_cd > here to create a new livecd and burn it.
I thought about this approach but then I decided to pursue the route of using relative paths instead. The reason for this is that my goal with the CVS checkout strategy is primarily educational. Instead of shielding a Catalyst newbie from the details of how to configure Catalyst and use it, what I am interested in doing is helping to explain it. As part of this approach, what I would like to do is to reduce the amount of error-prone typing a Catalyst newbie has to do in order to achieve their initial error-free target builds. Here is the directory structure that I am putting together in the CVS: CVS fsscript_file motd_file spec_files catalyst_config_files kernel_config_files portage_conf store_dir livecd_overlay root_overlay My goal is to have all of the configuration files needed to build targets contained within this directory structure. The ability for Catalyst to work with relative paths would significantly reduce the need for the user to edit the various paths that are present in the Catalyst config file and the spec files before they can attempt their initial target builds. Thank you, though, for your suggestion of using make or ant to help with Catalyst builds. Now that I know that others are using this approach I think I will experiment with it a bit to see how well it works :-) Ted Kosan [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
