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
content-class:	urn:content-classes:message
Subject:	RE: Should setup suggests to downgrade? [WAS: Lillypond for cygwin]
MIME-Version:	1.0
Date:	Sat, 6 Apr 2002 22:32:47 +1000
X-MimeOLE:	Produced By Microsoft Exchange V6.0.5762.3
Message-ID:	<FC169E059D1A0442A04C40F86D9BA76008AC50@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:	"Cliff Hones" <cliff AT aonix DOT co DOT uk>, <cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id g36CX5i19556

> -----Original Message-----
> From: Cliff Hones [mailto:cliff AT aonix DOT co DOT uk] 
> Sent: Saturday, April 06, 2002 7:03 PM

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

That's the point of the 'test' marking. And that's why currently curr
overrides test even if test is a higher version number.
 
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/

- Raw text -