Nelson Batalha wrote:
> Correct me if I'm wrong, but wouldn't it be easier to
just write a
> tiny script to "rsync" a local repository of
specs that Catalyst can
> already read?
>
> $ script.sh address/file.spec [options]
>
> it would sync and call catalyst [options]. There's the
advantage that
> you can easily modify this to pull in any way: scp,
www, etc, or just
> add protocol as an option.
>
> Just for Catalyst to "do one thing, do it
well" [1] ;).
>
>
> [1] http://e
n.wikipedia.org/wiki/Unix_philosophy
I'm not sure I'm following you.
The problem is that specfiles will be in different locations
depending
on host or environment:
f.e. /catalyst-prod and /catalyst-dev
or
/home/ramon/src/catalyst-images/portage_config/webserver and
/home/frank/src/server-images/portage_config/webserver
We'd like to have a single definition inside the specfiles
for a number
of the parameters, such as
portage_confdir = portage_config/webserver
instead of
portage_confdir
=/home/ramon/src/catalyst-images/portage_config/webserver
and
portage_confdir =
/home/ramon/src/catalyst-images/portage_config/webserver
How is this solved by rsyncing ?
I could write a makefile that substitutes variables in our
specfiles
dependant on /etc/catalyst/catalyst.conf but I was curious
whether this
was a more common use case and it didnt sound like such a
weird thing
to have, relative path support in catalyst specfiles.
>
> Get news, entertainment and everything you care about
at Live.com.
> Check it out! <http://www
.live.com/getstarted.aspx%20>
I got your email and about 18 copies with different
microsoft taglines.
Did you clickety-click or is M$ having mailserver issues ?
Ramon
--
gentoo-catalyst gentoo.org mailing list
|