| 1 |
On Tue, 18 Nov 2003 00:32:39 +0900 |
| 2 |
Jason Stubbs <jasonbstubbs@×××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Tuesday 18 November 2003 00:09, Markus Nigbur wrote: |
| 5 |
> > On Sun, 16 Nov 2003 23:18:09 -0500 (EST) |
| 6 |
> > |
| 7 |
> > "donnie berkholz" <spyderous@g.o> wrote: |
| 8 |
> > > I had imagined renaming anything that was *-update to config-* |
| 9 |
> > > also for consistency. |
| 10 |
> > |
| 11 |
> > Ehrm, IMHO *-update should be scripts that don't need any user |
| 12 |
> > interaction, like env-update or opengl-update (and yes, etc-update |
| 13 |
> > is an exception; even so it should really be called etc-config. ;) |
| 14 |
> |
| 15 |
> Umm, in a sense opengl-update does need interaction - even if it's |
| 16 |
> only passing command line parameters to the proggy. |
| 17 |
|
| 18 |
That's what i mean. User interaction is more than just specifiying some |
| 19 |
commandline options. Those could also be specified by a default file, |
| 20 |
a script calling the *-update script or simply default values. |
| 21 |
User interaction starts when the user actively has to do some stuff when |
| 22 |
running the script (as with etc-update). |
| 23 |
|
| 24 |
-- Markus |
| 25 |
|
| 26 |
-- |
| 27 |
Markus Nigbur |
| 28 |
Gentoo Developer |
| 29 |
http://www.gentoo.org |
Archives