Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Date:	Tue, 20 Nov 2001 20:07:43 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: -src package standard: proposal #5 and #5a
Message-ID:	<20011121010743.GA14791@redhat.com>
Reply-To:	cygwin-apps AT cygwin DOT com
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
References:	<3BF9B191 DOT 8FBDAA45 AT yahoo DOT com> <005901c17163$4db36cf0$b09d3fcb AT itdomain DOT net DOT au> <20011120015924 DOT GA9068 AT redhat DOT com> <042401c17169$a922cee0$0200a8c0 AT lifelesswks> <20011120023226 DOT GA9473 AT redhat DOT com> <OE45lk5wQlqlTPX4R0P00013cf7 AT hotmail DOT com> <20011120025230 DOT GA9596 AT redhat DOT com> <OE58bwKcbCxCDWo1dcJ00013e82 AT hotmail DOT com> <20011120103952 DOT H14154 AT cygbert DOT vinschen DOT de> <077201c17219$9fe9e7e0$0200a8c0 AT lifelesswks>
Mime-Version:	1.0
In-Reply-To:	<077201c17219$9fe9e7e0$0200a8c0@lifelesswks>
User-Agent:	Mutt/1.3.23.1i

On Wed, Nov 21, 2001 at 10:18:11AM +1100, Robert Collins wrote:
>
>===
>----- Original Message -----
>From: "Corinna Vinschen" <vinschen AT redhat DOT com>
>To: <cygwin-apps AT cygwin DOT com>
>Sent: Tuesday, November 20, 2001 8:39 PM
>Subject: Re: -src package standard: proposal #5 and #5a
>
>
>> Since everybody had a point now, I would like to add my two cent here.
>>
>> We just need two things in the new setup before the next rewrite:
>>
>> - New packages should be in `install', not in `skip' state.
>
>If you can suggest how to trivially identify said packages, sure.
>Otherwise, this should wait for installed.db to become a database - ie
>for rpm (does it have a database of available packages outside of
>rpmfind.net?) or deb compatability.

I don't agree that new packags should be automatically be marked as
install.  I think they should be presented in the correct state.
If the packages are selected via a category, or whatever, then they
should be installed, obviously.  Otherwise, I think they should just
be presented with a "Skip".

Tracking which packages are new could be handled by either modifying
installed.db to record all packages but mark them with their installed
state or to create a separate file.

A database would work too, of course.

>> - A One-Click "select all packages" button.  Hope Amazon doesn't read
>this.
>
>Thats what cgf and I just had a discussion on. I still don't see how a
>'select all packages' button will get clueless or new users to install
>what they need. And installing *everything* is exactly what we were
>trying to get away from. Clickable categories as well don't solve that.
>
>Still NMP.
>
>Chris, Corinna, please put heads together and decide: "select all
>packages button" or "clickable categories (so you can add a category
>'almost all' or whatever).
>
>Then tell me, and I'll code up the band aid for the categories branch.

I think that clickable categories is step one.

Adding a category to which everything belongs is step two.

Detecting package binary conflicts is step three.

Step three could be handled by upset.

cgf

- Raw text -