Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Tue, 2 Mar 2004 18:40:13 -0500 (EST)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: setup installation profiles [Was Re: invalid spawn id (4)]
In-Reply-To: <20040302215114.GC11909@redhat.com>
Message-ID: <Pine.GSO.4.56.0403021826350.17984@slinky.cs.nyu.edu>
References: <629E717C12A8694A88FAA6BEF9FFCD4403230E6C AT brigadoon DOT spirentcom DOT com> <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040302153052 DOT 03cfa770 AT 127 DOT 0 DOT 0 DOT 1> <Pine DOT GSO DOT 4 DOT 56 DOT 0403021604560 DOT 1337 AT slinky DOT cs DOT nyu DOT edu> <20040302215114 DOT GC11909 AT redhat DOT com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

On Tue, 2 Mar 2004, Christopher Faylor wrote:

> On Tue, Mar 02, 2004 at 04:10:00PM -0500, Igor Pechtchanski wrote:
> >Humor and indignation aside, it might be a useful feature to have
> >"installation profiles" for setup based on intended usage.  That way,
> >instead of having to wade through all the packages (on a too-small
> >screen, no less [an inside joke]), one could simply select "Cygwin for
> >telnet", or "Cygwin for shell scripting", or "Cygwin for cron" and the
> >right set of packages will automagically be selected.  Feel free to
> >implement the support for this in setup and submit a patch -- I'm sure
> >it will be thoughtfully considered.
>
> Actually, IMO, setup's UI needs a complete and total redesign.  It's
> obviously not very intuitive to use.  Something like the above would
> probably be useful but maybe we should just go with a more traditional
> installer look-and-feel.
>
> Anyone up for a 'setup2' project?
>
> cgf

AFAIK, there's already work in progress on separating setup's
functionality from the UI.  Once that's done, we could consider multiple
front-ends for setup, including a Linux-style TUI, or a skinned GUI.  My
suggestion above is orthogonal to this.

As for the traditional installer look-and-feel, if I understood you
correctly, it may not be appropriate for Cygwin, at least the component
selection interface.  I, personally, have some improvements that I'm
working on or planning to be working on that would bring the setup
procedure closer to that of the traditional installers.  I suppose by the
time we get to designing the look-and-feel, some examples and screenshots
would help determine exactly what people mean.  We're just about due for
another setup design discussion on cygwin-apps, anyway. :-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/