X-Spam-Check-By: sourceware.org Message-ID: <468AADEA.2070801@bonhard.uklinux.net> Date: Tue, 03 Jul 2007 21:13:30 +0100 From: fergus User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Cygwin ML CC: Igor Peshansky , fergus Subject: Re: [ANNOUNCEMENT] Setup.exe updated to version 2.573.2.2 References: <468AA95E.7030905@bonhard.uklinux.net> In-Reply-To: <468AA95E.7030905@bonhard.uklinux.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com And, absolutely the last word tonight, here is a hitherto undiscovered way in which old setup misbehaves and new setup does not. It might help locate any current procedural flaw in new setup. Unmount everything. Build a new directory c:\Cygwin\etc\setup and locate an up-to-date installed.db there (it need not be complete eg Base will do. If you already have c:\Cygwin temporarily rename it something else). Now use old setup to try to build a new Cygwin system under c:\Test (overwriting the default offering c:\Cygwin). Old setup misbehaves as follows: somewhere in its early progress it sneaks a look at c:\Cygwin, finds installed.db, and deduces there is nothing to do. New setup doesn't do this: it behaves properly, or appears to (at least in this role). Irrespective of the up-to-date installed.db lurking under c:\Cygwin, new setup respects the user's expressed wish to build under c:\Test, and goes ahead. Fergus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/