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
Message-ID:	<005201c1dd49$ce8bbce0$0101a8c0@albion>
From:	"Cliff Hones" <cliff AT aonix DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
References:	<FC169E059D1A0442A04C40F86D9BA76008AC49 AT itdomain003 DOT itdomain DOT net DOT au> <20020406062012 DOT GC12535 AT redhat DOT com>
Subject:	Re: Should setup suggests to downgrade? [WAS: Lillypond for cygwin]
Date:	Sat, 6 Apr 2002 10:02:38 +0100
Organization:	Aonix Europe Ltd.
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mimeole:	Produced By Microsoft MimeOLE V6.00.2600.0000

> setup should probably *never* suggest either going backwards or uninstalling.

Never say never?  Suppose a showstopper bug is found in a released
package - say one which could result in filestore or configuration
corruption.  The quickest solution would be to revert to the
previous version, and to make this painless (and avoid traffic here)
having the downgrade done automatically by setup would be nice.

A flag in setup.ini to indicate that a package version has been
withdrawn would do - something like "withdrawn : <version>".

Of course the correct solution would be to rebuild the previous
working version with a higher number, or even better, to fix the
bug, but sometimes time is of the essence.

-- Cliff



--
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/

- Raw text -