From: Chris Gianelloni <wolf31o2@gentoo.org>
To: steve@stevesworld.hopto.org
Cc: "Robin H. Johnson" <robbat2@gentoo.org>,
Gentoo Developers <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Installer For Gentoo
Date: Thu, 15 Jan 2004 10:33:28 -0500 [thread overview]
Message-ID: <1074180808.5866.134.camel@localhost> (raw)
In-Reply-To: <4006AD4F.90408@stevesworld.hopto.org>
[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]
On Thu, 2004-01-15 at 10:10, Stephen Clowater wrote:
> The configurations that are detected would only be the defaults, any
> user who wanted to change them, or bypass the entire install
> alltogether, could still do so. Indeed, you could specify a boot option
> like noinstaller and do the install the old way, or flip over to another
> vc (the installer would presumably be on vc/1) and continue the install
> by the guide instead of the installer.
>
> Its important to note the last thing that an installer would do would be
> to impose itself on the user. Its purpose is to provide some level of
> confort and prettyness for those who would like it, and to detect the
> most optimal defaults for a system, however, not to take away from the
> user the ability to change these defaults.
I think a much better way of even thinking about this would be rather
than running the installer at all, the user would type "install" or
"setup" at a prompt to start it.
> hmmm, perhaps having global use flags based on the selected packages,
> but have each package have the ability to override those USE flags when
> slelected? (default setting would be whatever global USE is)
Per-package USE flags is being worked on, but won't be around for a long
time. USE should never be determined by installed packages, but rather
always by the user.
netcat is a much better tool for such a task. I think I can speak for
most of us when I say that we feel very strongly about never adding
telnet to the default profiles, as it is simply inviting trouble.
--
Chris Gianelloni
Developer, Gentoo Linux
Games Team
Is your power animal a pengiun?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-15 15:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 16:02 [gentoo-dev] Installer For Gentoo Stephen Clowater
2004-01-14 17:28 ` Patrick Lauer
2004-01-14 20:57 ` Stephen Clowater
2004-01-14 21:09 ` Brian Dwornick
2004-01-14 22:08 ` Patrick Lauer
2004-01-14 23:34 ` Brian Dwornick
2004-01-15 0:14 ` Jeff Griffiths
2004-01-15 10:04 ` Paul de Vrieze
2004-01-16 3:50 ` Drake Wyrm
2004-01-15 3:47 ` Eric Sammer
2004-01-15 2:58 ` Robin H. Johnson
2004-01-15 15:10 ` Stephen Clowater
2004-01-15 15:33 ` Chris Gianelloni [this message]
2004-01-15 20:50 ` Paul de Vrieze
2004-01-16 7:31 ` John Nilsson
2004-01-21 8:25 ` John White
-- strict thread matches above, loose matches on Subject: below --
2002-05-31 21:31 [gentoo-dev] Installer for Gentoo Victor R. Prada
2002-06-01 8:49 ` Meir Kriheli
2002-06-01 9:20 ` Joshua Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1074180808.5866.134.camel@localhost \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=robbat2@gentoo.org \
--cc=steve@stevesworld.hopto.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox