Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
content-class: urn:content-classes:message
Subject: RE: Keeping base, adding standard.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Sat, 23 Mar 2002 16:30:23 +1100
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <FC169E059D1A0442A04C40F86D9BA76008AB7F@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-apps AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g2N5UV212230



> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com] 
> Sent: Saturday, March 23, 2002 4:21 PM

> >This comes back to what I said some time ago - that categories are 
> >necessary but not sufficient to provide a good user experience.

 
> Yadda, yadda.  I've said it all before.

Likewise.
 
> >Something like 'configurations' are needed (which may indeed be 
> >categories under the skin) that builds user focused 

> You're very unhappy with overloading categories while this is 
> exactly what I had envisioned when I suggested them.  And, I 
> strongly disagree with the above way of dealing with things.

Why? (Not trying to be dificult here).
 
> I hope this doesn't mean that I have to go back to 
> maintaining setup but I don't think anyone is going to 
> convince me that adding another layer to the process is going 
> to improve the user experience.

You are of course welcome to resume the mantle anytime you feel the
need. I'm surprised that a discussion point would bring it up though. I
certainly haven't threatened any "I won't do this" or suggested that
it's "my way or the highway". And as no setup.exe changes are needed to
do what you're proposing, my being setup maintainer is quite orthogonal
to my point of view on that.

> >OTOH leveraging dependencies via meta-packages to achieve it makes a 
> >lot of sense to me, the question is how to present it to the 
> user in a 
> >meaningful way.
> 
> Sorry.  I don't know what this means.  If you mean allowing 
> the addition of category names to dependencies then I think 
> that's a great idea.

I hadn't thought of that, but have no objection to it being done. I
can't think of any immediate use for it though.

What I meant was that if you want the user to select "Standard" and get
the packages you listed as being 'standard' installed, creating an empty
tarball that depends on those packages will do that.

Rob