| 1 |
On Tue, 2004-03-16 at 15:59, Jason Rhinelander wrote: |
| 2 |
> That said, 'xyz-(update|config)' makes more /natural/ sense. If I know |
| 3 |
> that I need to run the module script, I can hit 'module<tab>' and get |
| 4 |
> the right script, or at least a small list of commands. Likewise for |
| 5 |
> most others (though some need a '-' for tab-completion purposes): |
| 6 |
> opengl, etc, gcc, etc. I don't know about you, but normally when I'm |
| 7 |
> using one of these tools I have an express purpose in mind: "change |
| 8 |
> opengl libraries," "change to a different gcc," "see if any etc files |
| 9 |
> have updates," "update my kernel module dependencies", etc. My purposes |
| 10 |
> are generally not "see what configuration I can change today." |
| 11 |
|
| 12 |
How do you know a config tool exists? I don't sit around entering every |
| 13 |
binary name on my system, then hitting tab to see whether there's a |
| 14 |
*-config to go along with it. |
| 15 |
|
| 16 |
> What about the possibility of some sort of configuration script wrapper? |
| 17 |
> Call it "update", for the sake of simplicity. Then I could run: |
| 18 |
> |
| 19 |
> update gcc |
| 20 |
> update opengl |
| 21 |
> update modules |
| 22 |
> update etc |
| 23 |
> |
| 24 |
> Then various *-config and *-update programs could register themselves |
| 25 |
> somehow, so that "update --help" could list all the things that can be |
| 26 |
> updated on the current system, and could (and should) even include |
| 27 |
> descriptions of what the various commands do. Someone could then write |
| 28 |
> a fairly trivial bash-completion script to allow 'update <tab><tab>' to |
| 29 |
> list all the configuration tools on my system, but good old 'etc-update' |
| 30 |
> would still be there when my first thought is "etc" instead of "update". |
| 31 |
|
| 32 |
Interesting idea. When will you have the prototype coded? |
| 33 |
|
| 34 |
I'm being realistic here. Baby steps. This is the first step -- maybe |
| 35 |
something like your idea lies in the future. |
| 36 |
|
| 37 |
> * (As a side note, to the end of uniformity, opengl-update should |
| 38 |
> probably change to config-opengl (or opengl-config), since it has more |
| 39 |
> in common with the other 'config' scripts than 'update' scripts. |
| 40 |
> 'update' should mean "update my system," while 'config' should mean |
| 41 |
> "change something on my system" - where "something" can generally be |
| 42 |
> changed back with the same tool.) |
| 43 |
|
| 44 |
I already said this. |
| 45 |
|
| 46 |
Donnie |
| 47 |
-- |
| 48 |
Donnie Berkholz |
| 49 |
Gentoo Linux |
Archives