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
X-Server-Uuid:	2d3b7162-db1d-11d3-b8ee-0008c7dfb6f1
Message-ID:	<718198F862F1D411B10F0002A50A4DB10B8281DB@e90wwce3.dx.deere.com>
From:	"Polley Christopher W" <PolleyChristopherW AT JohnDeere DOT com>
Reply-to:	cygwin AT cygwin DOT com
To:	"'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject:	RE: cygwin archive? (previous versions for fallback)
Date:	Wed, 12 Mar 2003 08:09:47 -0600
MIME-Version:	1.0
X-WSS-ID:	1271E0382881040-01-02

>From: Igor Pechtchanski [mailto:pechtcha AT cs DOT nyu DOT edu]
>On Tue, 11 Mar 2003, Jason Tishler wrote:
>
>> [snip]
>> However, Cygwin setup.exe's cache should have all previous versions
>> installed including PostgreSQL unless one deletes them.  
>Hence, the old
>> PostgreSQL version should still have been available for the pg_dump
>> phase.
>>   Jason
>
>Not if it's not present in the newly downloaded setup.ini, I don't
>think...

No, unless the user takes steps to clean out the download directory (with
Michael Chase's clean_setup.pl script, for example) all previously
downloaded tarballs persist.  

Being able to installing one of those previous tarballs with setup is
another story, though.  One way that I know of is to force setup to put the
packages of interest into the Misc category.

Regards,
Chris


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