Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Mon, 05 Nov 2001 23:32:04 EST To: cygwin-apps AT cygwin DOT com Subject: Re: Setup.exe - snapshot runs but compiled from cvs get application error. X-Mailer: Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va Message-Id: From: Brian Keener Reply-To: bkeener AT thesoftwaresource DOT com In-Reply-To: References: Robert Collins wrote: > Anyway, the question is, what should download only do? Should it present > the root IDD to select the root for cygwin? I've modified it to do that > and I'll be checking in shortly. I saw your message about trying the latest HEAD but let me address this question first. What will happen if I am doing a Download only for a new install - will I truly be able at that point in time to select my root for cygwin or would I want to in all cases - yes we could but what of other newbies?? As to the above - my personal thought is download only should not ask for the root - it should only ask for the local cache. Perhaps it should work the same way we used to (and may still) handle setup.log and setup.log.full. The directory they reside in is based on the type on install - Ie they are in root directory if you select install from local directory or install from internet and they reside in the same place setup.exe exists if you selected a download from internet. Of course the above may not work with some of the changes y'all are trying to implement but I would think the file that remembers the local cache and for that matter the setup.log and setup.log.full really belong wherever setup.exe resides - not where the local cache actually is or where cygwin itself will reside. Just my $.02 worth.