[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] Re: talk amongst yourselves: "iterated" operations over
From: |
Miles Bader |
Subject: |
[Gnu-arch-users] Re: talk amongst yourselves: "iterated" operations over configs |
Date: |
16 Sep 2003 14:33:33 +0900 |
Robert Anderson <address@hidden> writes:
> tla catcfg | awk '{print $1}' | xargs -n1 -i tla what-changed --dir
>
> There's quite a few commands which could be "iterated" like this over
> the project trees in a config. I think it's worth thinking about a way
> of trying to systematize such operations and build them into the cli.
>
> My first guess at a decent cli is to provide an argument analogous to
> the usual --dir argument; I guess --config is the most obvious choice.
I agree that this is worth improving, but I'm not sure what your
suggestion is; do you mean that --config would take a config argument
(like build-config does), and apply that config similar to the pipeline
you suggested above?
I think that would be annoying since it would require you to always
specify the config.
In my current usage, I've used Tom's config to make my tla source tree,
but I don't really want to use the original config after that, because
I've replaced parts of the tree with my own.
Because of this I use a similar, but crucially different, pipeline:
tla inventory --trees --nested | xargs -n1 tla CMD --dir
For this particular usage, a similar `--nested' option would be very
convenient, e.g., the above would be replaced by:
tla CMD --nested
As for --config, well, I'm not yet a willing user, so I'll leave that
to others, but it does seem like it would be annoying to have to keep
track of the config; maybe if build-config stashed away the config name
in {arch}/=current-config it could be read by --config or something...
-Miles
--
We live, as we dream -- alone....
Re: [Gnu-arch-users] talk amongst yourselves: "iterated" operations over configs, Robert Anderson, 2003/09/16