Re: Relative paths in spec files

Andrew Gaffney wrote:
> With catalyst, there are so many paths that could be
the "root" 
> (/var/tmp/catalyst, /etc/catalyst, some random dir
where you store your 
> specs, etc.) that it just doesn't work.

I'm not sure that's a problem in everyone's environment.

In my case, I want to be able to check my complete set of
configuration 
for catalyst (spec files, overlays, linuxrc replacements,
etc etc) into 
subversion and have it Just Work regardless of exactly where
the user 
checks it out to. The key here is that because things are
stored in 
subversion in a specific tree layout, I know with certainty
what the 
relative paths look like on-disk, but I know nothing at all
about the 
absolute path.

Now, I can do this by hand by checking .spec.in files into
svn and 
preprocessing them, but that's ugly as sin; I'd much prefer
to make 
catalyst/modules/parse_spec.py support environment variable
substitution 
or somesuch, at least if `yall (agaffney, chris) would
accept such a patch.

Would $ be acceptable to substitute in environment
variables 
(with $ being special), or would this stomp on some
other 
legitimate syntax?

-- 
gentoo-catalystgentoo.org mailing list