| 1 |
On Tue, 2007-04-24 at 10:41 -0400, John Eckhart wrote: |
| 2 |
> I often build different types of images using variations on the |
| 3 |
> spec files and in order to not pollute my tested working environments, |
| 4 |
> I copy the whole thing into a new dir. I currently use some sed magic |
| 5 |
> to set the absolute paths but if catalyst used relative paths it would |
| 6 |
> make life just a little better. |
| 7 |
|
| 8 |
I guess I just don't get why people are putting paths they know are |
| 9 |
going to be variable in a spec file. |
| 10 |
|
| 11 |
Example stage1.spec: |
| 12 |
subarch: x86 |
| 13 |
target: stage1 |
| 14 |
rel_type: default |
| 15 |
profile: default-linux/x86/no-nptl |
| 16 |
chost: i486-pc-linux-gnu |
| 17 |
|
| 18 |
Example script: |
| 19 |
#!/bin/bash |
| 20 |
version=$1 |
| 21 |
source=$2 |
| 22 |
|
| 23 |
catalyst -f stage1.spec -c /path/to/some/catalyst.conf -C version_stamp= |
| 24 |
$version snapshot=$version source_subpath=$source |
| 25 |
|
| 26 |
Remember that you don't have to have everything in the spec file. |
| 27 |
There's no need for any sed-fu, at all. Simply have your script provide |
| 28 |
whatever it is that you want and give it to catalyst via -C on the |
| 29 |
command line, which works in conjunction with the -f specfile options. |
| 30 |
|
| 31 |
-- |
| 32 |
Chris Gianelloni |
| 33 |
Release Engineering Strategic Lead |
| 34 |
Alpha/AMD64/x86 Architecture Teams |
| 35 |
Games Developer/Council Member/Foundation Trustee |
| 36 |
Gentoo Foundation |
Archives