On Tue, 2007-04-24 at 10:41 -0400, John Eckhart wrote: > I often build different types of images using variations on the > spec files and in order to not pollute my tested working environments, > I copy the whole thing into a new dir. I currently use some sed magic > to set the absolute paths but if catalyst used relative paths it would > make life just a little better.
I guess I just don't get why people are putting paths they know are going to be variable in a spec file. Example stage1.spec: subarch: x86 target: stage1 rel_type: default profile: default-linux/x86/no-nptl chost: i486-pc-linux-gnu Example script: #!/bin/bash version=$1 source=$2 catalyst -f stage1.spec -c /path/to/some/catalyst.conf -C version_stamp= $version snapshot=$version source_subpath=$source Remember that you don't have to have everything in the spec file. There's no need for any sed-fu, at all. Simply have your script provide whatever it is that you want and give it to catalyst via -C on the command line, which works in conjunction with the -f specfile options. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer/Council Member/Foundation Trustee Gentoo Foundation
signature.asc
Description: This is a digitally signed message part
