X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_20 X-Spam-Check-By: sourceware.org Message-ID: <4B3315BB.3000406@bonhard.uklinux.net> Date: Thu, 24 Dec 2009 07:18:19 +0000 From: Fergus User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Cygwin ML CC: Fergus Subject: How to install Legacy from scratch? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Thanks for great new version. 1.7 uses setup.ini, draws from release/, uses setup.exe v.2.673. 1.5 uses setup-legacy.ini, draws from release-legacy/, uses setup.exe v.2.673 (i.e. the same version as 1.7). My question is: how does a user install 1.5 from scratch (if desired or needed e.g. old faithful W98SE machine)? One way is to download setup.exe, setup-legacy.ini and the entire release-legacy/*, change the .ini filename to setup.ini and then run setup.exe as a local install. (Actually I haven't tried this yet, will one additionally have to rename the directory release-legacy/ to release/ and change all instances of release-legacy/ where they occur in the .ini file to release/? I guess it depends what setup.exe is expecting and whether the term release-legacy will trip it up.) But how to manage a web install? Thanks. Fergus -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple