From: DJ Cozatt <user99@bellsouth.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] GUI installer
Date: Tue, 15 Apr 2003 09:26:31 -0500 [thread overview]
Message-ID: <20030415092631.6a8fe185.user99@bellsouth.net> (raw)
In-Reply-To: <1050275603.16939.37.camel@melvin.lorax.wox.org>
On 13 Apr 2003 18:13:23 -0500
Alec Berryman <alec@lorax.wox.org> wrote:
> On Sun, 2003-04-13 at 17:33, Derek J. Belrose wrote:
> > Well the X install is in the future it seems. I think gentoo would
> > benefit from a cli install/package manager more than it currently has.
>
Saw several posts to this thread that included suggestions from other distro's. Did not see the slack pkg managemnt as a suggestion. It is based on ncurses and includes sublevels of install types for "expert"
"newbie" and another can't remember the label now(full?). The idea is to give users a choice for controlling installation packages that is consistent with their knowledge level on what is installed. Don't know if it's gpl.
There is also a Slackbuild script that does source installs. IIRC
> <snip>
>
> > It should work over serial line consoles as well as local displays.
> > It should be really easy for a beginner, yet possible for the most
> > advanced user to take control at any point.
>
> http://forums.gentoo.org/viewtopic.php?p=275364#275364
>
> Yesterday "optilude" posted a "fast and flexible curses ebuild browser"
> to the Gentoo Forums.
>
> Requiring only bash and dialog, it would easily fit onto the
> traditionally minimal Gentoo install CD and alongside ufed and
> mirrorselect. More importantly, because it works directly through
> emerge (emerge `ebb` is the suggested invocation), using this ebuild
> browser would preserve flexibility in the Gentoo install: for those who
> would prefer to stick with the traditional emerge command-line
> interface, this browser would not interfere with complete control over
> emerge, but for those who do want the browser it is easily accessible.
> Give it a shot.
>
> --
>
> Alec Berryman <alec@lorax.wox.org>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-15 13:21 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 23:04 [gentoo-dev] GUI installer Jeff Rose
2003-04-11 23:25 ` Riyad Kalla
2003-04-12 0:05 ` Alec Berryman
2003-04-12 2:19 ` Brian Harring
2003-04-12 3:52 ` George Shapovalov
2003-04-13 5:05 ` Justin Whitney
2003-04-13 5:38 ` Derek J. Belrose
2003-04-13 6:50 ` Cliff Free
2003-04-13 7:08 ` Derek J. Belrose
2003-04-13 8:49 ` Jeff Rose
2003-04-13 9:14 ` Derek J. Belrose
2003-04-13 9:23 ` Cedric Veilleux
2003-04-13 9:30 ` Derek J. Belrose
2003-04-13 9:34 ` Brian Harring
2003-04-13 9:47 ` Derek J. Belrose
2003-04-13 13:55 ` Cliff Free
2003-04-18 9:35 ` Mark Bainter
2003-04-18 14:54 ` Jeff Rose
2003-04-19 3:45 ` Abhishek Amit
2003-04-20 2:50 ` Evan Powers
2003-04-20 3:05 ` C. Brewer
2003-04-13 16:33 ` Alain Penders
2003-04-13 20:04 ` Jeff Rose
2003-04-13 20:09 ` Graham Forest
2003-04-13 20:36 ` Derek J. Belrose
2003-04-13 22:26 ` Cliff Free
2003-04-13 22:33 ` Derek J. Belrose
2003-04-13 23:13 ` Alec Berryman
2003-04-15 14:26 ` DJ Cozatt [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-14 10:18 Stroller
2003-04-14 13:17 ` William Hubbs
2003-04-15 4:06 ` John Nilsson
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=20030415092631.6a8fe185.user99@bellsouth.net \
--to=user99@bellsouth.net \
--cc=gentoo-dev@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