X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Message-ID: <4978A35E.6050702@etr-usa.com> Date: Thu, 22 Jan 2009 09:48:30 -0700 From: Warren Young User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: 1.5 / 1.7 setup.exe entanglement? References: <49779B20 DOT 9060905 AT etr-usa DOT com> <20090122111211 DOT GA17948 AT calimero DOT vinschen DOT de> In-Reply-To: <20090122111211.GA17948@calimero.vinschen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Corinna Vinschen wrote: > > Yes, the reason is that setup looks into c:\cygwin by default and if it > finds setup files there, it will use them Thought so. A wishlist item, then: add something to 1.5's setup.exe to detect that c:\cygwin is from a later version, and refuse to use information found there. It should behave no differently in this case than installing Cygwin 1.5 on a fresh machine. On detecting this, it could also modify the default install location to c:\cygwin-1.5 or similar, on the theory that you probably don't want to overwrite the newer installation. Again, the reason to do this is that after 1.7 gets released, we'll probably still see a fair number of people having to install 1.5 alongside it, and you can't count on them to install 1.5 first, or go through the procedure you outlined to keep the installs disentangled. -- 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/