Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Sun, 27 May 2001 16:02:32 EDT
To:	cygwin AT cygwin DOT com
Subject:	Re: Setup.exe v2.56
X-Mailer:	Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va
Message-Id:	<VA.000007be.0051cc9b@thesoftwaresource.com>
From:	Brian Keener <bkeener AT thesoftwaresource DOT com>
Reply-To:	bkeener AT thesoftwaresource DOT com
In-Reply-To:	<00af01c0e680$0afc8ea0$562fa4cb@brasd1.vic.optushome.com.au>
References:	<20010527031018 DOT A14119 AT redhat DOT com> <00af01c0e680$0afc8ea0$562fa4cb AT brasd1 DOT vic DOT optushome DOT com DOT au>

Travis Howell wrote:
> A install from local download (When a user downloads all Cygwin setup binary
> tarballs to one directory and launches setup from there, no setup.ini
> exists) still fails to registered installation of parts (They show up as new
> 2nd time setup in run) and setup lists all parts as just öX  now instead of
> their correct filenames.

Even during an install from local directory you need the setup.ini and you need 
to preserve the download directory structure. If you do not they will all show 
as new the next time around.  If you move the download to another directory you 
should move setup.ini also and preserve the structure.

bk



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -