public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Riyad Kalla" <rsk@u.arizona.edu>
To: "'Jeff Rose'" <rosejn@Colorado.EDU>, <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] GUI installer
Date: Fri, 11 Apr 2003 16:25:13 -0700	[thread overview]
Message-ID: <000b01c30081$9ab21890$d628c480@rskwork> (raw)
In-Reply-To: <Pine.GSO.4.40.0304111631160.27357-100000@ucsub.colorado.edu>

Jeff there is an installer in the works called Cursing Cow, I forgot who
was working on it, but I'm sure they'll reply soon enough...

Best,
-Riyad

> -----Original Message-----
> From: Jeff Rose [mailto:rosejn@Colorado.EDU]
> Sent: Friday, April 11, 2003 4:04 PM
> To: gentoo-dev@gentoo.org
> Subject: [gentoo-dev] GUI installer
>
>
> Hello,
> 	I'm pretty new to gentoo, but I am an instant convert.
> Just a few months of emerge bliss and now I'm an avid
> supporter.  Anyway, I'm thinking about starting a summer
> project and I'm pondering the idea of a gui installer.  I've
> been looking around a bit and it doesn't look like anyone is
> working on one.  Is that true?  If there isn't already a
> project then I think I'll give it a whirl.  I know, I know,
> gentoo is so great because it allows you to customize and
> tweak the hell out of everything. That is completely true.
> So, an installer would have to allow just as much but it
> could take care of the mundane details for those who aren't
> interested or knowledgable enough.
> 	I haven't been around to see what people discuss in
> terms of the installer so I'm sorry if this is all stuff that
> you have gone over hundreds of times.  Even more minimal than
> a gui installer, have you thought about adding more scripts
> to do the standard directory setup, download, chroot... type of stuff?
> 	What do you think?
>
> -Jeff
>
>
> --
> gentoo-dev@gentoo.org mailing list
>


--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-11 23:25 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 [this message]
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
  -- 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='000b01c30081$9ab21890$d628c480@rskwork' \
    --to=rsk@u.arizona.edu \
    --cc=gentoo-dev@gentoo.org \
    --cc=rosejn@Colorado.EDU \
    /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