Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 12 Mar 2003 11:20:47 -0500 From: Jason Tishler Subject: Re: cygwin archive? (previous versions for fallback) In-reply-to: <718198F862F1D411B10F0002A50A4DB10B8281DB@e90wwce3.dx.deere.com> To: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20030312162047.GB1532@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <718198F862F1D411B10F0002A50A4DB10B8281DB AT e90wwce3 DOT dx DOT deere DOT com> On Wed, Mar 12, 2003 at 08:09:47AM -0600, Polley Christopher W wrote: > >From: Igor Pechtchanski [mailto:pechtcha AT cs DOT nyu DOT edu] > >On Tue, 11 Mar 2003, Jason Tishler wrote: > >> 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. > > > >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. Exactly. > 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. I have used "Install from Local Directory" and setting the "Local Package Directory" to the directory containing the tarball successfully in the past. Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/