public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Murphy <poisonbl@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: stage3 only for i486?
Date: Thu, 4 Apr 2013 08:30:33 -0400	[thread overview]
Message-ID: <CAOTuDKqbCkF1jhxNFjKdcPsOE-kmMtiz8ULHeEbZnoOkNOQ9rw@mail.gmail.com> (raw)
In-Reply-To: <515D428F.5080506@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

I


On Thu, Apr 4, 2013 at 5:06 AM, Alan McKinnon <alan.mckinnon@gmail.com>wrote:

> On 04/04/2013 10:15, Yuri K. Shatroff wrote:
> > Well, an installer certainly would find its users. But none is perfect,
> > and writing another (imperfect) one exclusively for Gentoo is sort of
> > wasting time. A "true" Gentoo way IMO would be a selection of installers
> > on the installation medium ;-) But AFAICT it is this idea that wouldn't
> > be popular, rather than leaving no-installer at all.
>
> A true GentooWay installer would be any installer of your own choice
> that launches the shell of your chosing, accepts any stage3 tarball that
> you want and gotten from anywhere you choose to get it, and unpacked any
> place you feel like putting it. It will then run the software of your
> choice and install whatever you tell it to.
>
> That's an awful lot of "your choices" :-)
>
>
>
> --
> Alan McKinnon
> alan.mckinnon@gmail.com
>
>
>
Isn't that exactly what the guide itself is? The only thing it doesn't make
explicit is the choice of package manager and choice of shell, though that
itself could be considered an advanced feature available to those
experienced enough to know they want the choice, who are, I would
hope, knowledgeable enough to make and enact that choice at the appropriate
point in the install. The only feature the guide lacks is a pretty point
and click interface that either over-clutters the user with options or
denies them choices they might want, which I might add, the same could be
said of portage itself.

-- 
Poison [BLX]
Joshua M. Murphy

[-- Attachment #2: Type: text/html, Size: 2162 bytes --]

  reply	other threads:[~2013-04-04 12:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 17:51 [gentoo-user] stage3 only for i486? Davide Carnovale
2013-04-02 18:12 ` Michael Hampicke
2013-04-02 18:17 ` Bruce Hill
2013-04-02 18:31   ` Davide Carnovale
2013-04-02 19:17 ` Alan McKinnon
2013-04-02 19:40   ` Davide Carnovale
2013-04-02 20:28     ` Alan McKinnon
2013-04-03 18:44       ` [gentoo-user] " James
2013-04-03 19:36         ` Alan McKinnon
2013-04-04  3:05           ` [gentoo-user] " Stroller
2013-04-04  7:48             ` Davide Carnovale
2013-04-04  8:15           ` [gentoo-user] " Yuri K. Shatroff
2013-04-04  9:06             ` Alan McKinnon
2013-04-04 12:30               ` Joshua Murphy [this message]
2013-04-04 18:02               ` Philip Webb
2013-04-02 23:41   ` [gentoo-user] " Daniel Frey
2013-04-03  1:20     ` Raymond Jennings
2013-04-03  7:59     ` Alan McKinnon
2013-04-03 15:37       ` Peter Humphrey
2013-04-03 19:14         ` Alan McKinnon
2013-04-02 21:01 ` Francesco Talamona
2013-04-02 22:02   ` Davide Carnovale

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=CAOTuDKqbCkF1jhxNFjKdcPsOE-kmMtiz8ULHeEbZnoOkNOQ9rw@mail.gmail.com \
    --to=poisonbl@gmail.com \
    --cc=gentoo-user@lists.gentoo.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