| 1 |
On Fri, Apr 30, 2004 at 09:36:56AM +1200, Nick Rout wrote: |
| 2 |
> |
| 3 |
> On Thu, 29 Apr 2004 17:32:04 -0400 (EDT) |
| 4 |
> Ajai Khattri <ajai@××××.net> wrote: |
| 5 |
> |
| 6 |
> > On Fri, 30 Apr 2004, Eldad Zack wrote: |
| 7 |
> > |
| 8 |
> > > The best way is to allow run-time configuration in /etc files. |
| 9 |
|
| 10 |
I don't like the idea. I know it from Debian. For Debian it's ok, but |
| 11 |
gentoo is different. |
| 12 |
|
| 13 |
> some ebuilds tell you to run a configuration script after the ebuild |
| 14 |
> completes (although often this disappears in the other cruft that emerge |
| 15 |
> throws past you) |
| 16 |
|
| 17 |
In my opinion, that's the best argument for using a run-time |
| 18 |
configuration. |
| 19 |
But even this wouldn't work out. I've got a celeron 333MHz, which is |
| 20 |
running gentoo. I don't want to look after my machine every hour to |
| 21 |
receive a new "run-time configuration"-instruction. ;) |
| 22 |
So you would need at least some kind of "default-choice" for people, |
| 23 |
that do not want to be asked. |
| 24 |
|
| 25 |
I would prefer an update logfile, which can be viewed and deleted with |
| 26 |
etc-update. This log could keep all hints, which have been made during |
| 27 |
the last update. |
| 28 |
|
| 29 |
Bis denne, |
| 30 |
Aiko |
| 31 |
|
| 32 |
-- |
| 33 |
.~. Aiko Barz |
| 34 |
/v\ |
| 35 |
// \\ Mail: aiko@××××××.de |
| 36 |
/( _ )\ Web: http://www.chroot.de |
| 37 |
^^ ^^ PGP: http://www.chroot.de/index.php?navi=GnuPG |
Archives