| 1 |
On Thu, 2004-01-15 at 10:10, Stephen Clowater wrote: |
| 2 |
> The configurations that are detected would only be the defaults, any |
| 3 |
> user who wanted to change them, or bypass the entire install |
| 4 |
> alltogether, could still do so. Indeed, you could specify a boot option |
| 5 |
> like noinstaller and do the install the old way, or flip over to another |
| 6 |
> vc (the installer would presumably be on vc/1) and continue the install |
| 7 |
> by the guide instead of the installer. |
| 8 |
> |
| 9 |
> Its important to note the last thing that an installer would do would be |
| 10 |
> to impose itself on the user. Its purpose is to provide some level of |
| 11 |
> confort and prettyness for those who would like it, and to detect the |
| 12 |
> most optimal defaults for a system, however, not to take away from the |
| 13 |
> user the ability to change these defaults. |
| 14 |
|
| 15 |
I think a much better way of even thinking about this would be rather |
| 16 |
than running the installer at all, the user would type "install" or |
| 17 |
"setup" at a prompt to start it. |
| 18 |
|
| 19 |
> hmmm, perhaps having global use flags based on the selected packages, |
| 20 |
> but have each package have the ability to override those USE flags when |
| 21 |
> slelected? (default setting would be whatever global USE is) |
| 22 |
|
| 23 |
Per-package USE flags is being worked on, but won't be around for a long |
| 24 |
time. USE should never be determined by installed packages, but rather |
| 25 |
always by the user. |
| 26 |
|
| 27 |
netcat is a much better tool for such a task. I think I can speak for |
| 28 |
most of us when I say that we feel very strongly about never adding |
| 29 |
telnet to the default profiles, as it is simply inviting trouble. |
| 30 |
|
| 31 |
-- |
| 32 |
Chris Gianelloni |
| 33 |
Developer, Gentoo Linux |
| 34 |
Games Team |
| 35 |
|
| 36 |
Is your power animal a pengiun? |
Archives