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: Fri, 02 Nov 2001 13:43:47 EST
To: cygwin AT cygwin DOT com
Subject: Re: A bug (?) in the current setup.exe 2.78.2.15
X-Mailer: Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va
Message-Id: <VA.00000997.00e8276f@thesoftwaresource.com>
From: Brian Keener <bkeener AT thesoftwaresource DOT com>
Reply-To: bkeener AT thesoftwaresource DOT com
In-Reply-To: <3BE2E375.EB32B4E4@syntrex.com>
References: <001201c163a7$5d1610e0$6fc82486 AT medschool DOT dundee DOT ac DOT uk> <3BE2E375 DOT EB32B4E4 AT syntrex DOT com>

Pavel Tsekov wrote:
> So one solution which comes to me is remove the scan_downloaded_files if
> there is 
> no setup.ini install. But since its complicated topic I'll wait for
> somone elses
> opinion :)
>
Actually, scan_downloaded_files is there for exactly that purpose - setup at 
one time was supposed to be able to pick up packages that were not part of 
setup.ini and be able to install them, it was also supposed to be able to pick 
up older versions that might not be listed in setup.ini for packages setup.ini 
knows about and put those in the chooser options for install as well (usually 
only in install from local directory mode) provided their was an open spot in 
the structure.

That said - with all the current changes for categories and dependencies and 
the reliance of setup on setup.ini and setup.hint it would appear that the days 
of setup simply picking up packages out of the directory and installing them is 
probably past. 




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