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>
Delivered-To:	mailing list cygwin-apps AT cygwin DOT com
Date:	Sun, 23 Dec 2001 13:43:28 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-apps AT cygwin DOT com, cygwin AT cygwin DOT com
Subject:	Re: Setup.exe snapshot
Message-ID:	<20011223184328.GB21163@redhat.com>
Reply-To:	cygwin-apps AT cygwin DOT com
Mail-Followup-To:	cygwin-apps AT cygwin DOT com, cygwin AT cygwin DOT com
References:	<02b801c18bb1$ad62f360$0200a8c0 AT lifelesswks>
Mime-Version:	1.0
In-Reply-To:	<02b801c18bb1$ad62f360$0200a8c0@lifelesswks>
User-Agent:	Mutt/1.3.23.1i

On Sun, Dec 23, 2001 at 11:59:33PM +1100, Robert Collins wrote:
>* Dependencies will only trigger installation of a package - they won't
>force an upgrade of an installed package. (with the caveat that in the
>future versioned dependencies may force upgrades).

Isn't this what has consistently gotten us into trouble?  Why not force
an update of a package if a package that depends on it is being upgraded?
This seems more intuitive to me.

Also, if we have no way to install all packages, then I think this new
release should be delayed.  We've been promising this for months.

If all that we need, however, is for upset to add things to a "Full"
category, which can be selected, I can do that.

cgf

- Raw text -