Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Subject: Re: New Install May Have a Bug
From: Robert Collins <robert.collins@itdomain.com.au>
To: Charles Wilson <cwilson@ece.gatech.edu>
Cc: Heribert Dahms <heribert_dahms@icon-scm.com>,
   Mark Jones
	 <mark_umr@excite.com>,
   Stephano Mariani <sk.cygml@btinternet.com>, cygwin@cygwin.com
In-Reply-To: <3C041931.1010405@ece.gatech.edu>
References: 
	<BF35D9C143BCCC4EB63181B67C9320C83A9AD6@serv-075.icon-germany.local>
	<1006900876.2028.12.camel@lifelesswks>  <3C041931.1010405@ece.gatech.edu>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 28 Nov 2001 09:55:30 +1100
Message-Id: <1006901730.2028.18.camel@lifelesswks>
Mime-Version: 1.0

On Wed, 2001-11-28 at 09:52, Charles Wilson wrote:
> Robert Collins wrote:

> > What you are talking about is metapackages, which are implemented via
> > categories, but need a new screen to allow the choice - simply for user
> > clarity - as setup.exe can handle those packages now.
> 
> 
> Right, but the 'Base' category is both a "category" in the sense you 
> describe, AND a metapackage(sortof) -- simply because everything in 
> 'Base' is automatically installed.
> 
> Hence "add foo to 'Base'" really means "add foo to 'required' metapackage".
> 
> But I get what you're saying; 'Base' seems to be THE special case.  In 
> all other cases, 'categories' != 'metapackage'
> 

Thanks for putting so clearly Chuck, yes that is what I am saying.

Rob


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/