Message-Id: <200504281306.j3SD6iHO011572@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Reply-To: From: To: Cc: Subject: Bespoke installations: simple elegance of setup.exe when setup.ini is absent Date: Thu, 28 Apr 2005 14:02:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-UoD-Spam-Score: -4.7 (----) X-UoD-Spam-Report: -------------------------------------------------- This message has been scanned by a SpamAssassin installation on the spam checking server hughnew at the University of Dundee. Content analysis details: (-4.7 hits, 5.0 required) 0.2 NO_REAL_NAME From: does not include a real name -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0001] X-UoD-Scan-Signature: 20eaa71d3e1f59c0a2c21fb4446c9ab1 Note-from-DJ: This may be spam About 3 years ago the then available setup.exe used to work as follows; for some quite long period since, it didn't (the installation hung); now it's back to its old (possibly unintended) functionality. Or so it seems to me. Can anybody confirm? To install Cygwin in full or in part, place all required *.bz2 in their correct location under c:\MyCyg\release\ or (conveniently and repeatably) on a CD under d:\MyCyg\release\. Do _not_ include any version of setup.ini under c:\MyCyg\, where conventionally this file would be located. Run setup.exe, choosing to "Install from Local Directory" identified as [cd]:\MyCyg\. All the included packages will be shown under Misc. Click the selector to change from "Default" to "Install" and away you go, to achieve a full installation of your included packages. Note: "all required *.bz2": this phrase of course is a can of worms and unless the dependencies have been attended to by a previous use of setup.ini, this method of installation carries with it the risk that some packages will be installed whilst lacking necessary companions. But, if you are sure what you want and that you are getting it, this method (which seems to work) saves you any previously suggested hassle-rich approaches including tedious repeated point and click selection of packages from a list of ?> 500, special management of installed.db or setup.ini, or the creation of tailored local mirrors, copying from other media, careful use of mount and umount, or combinations of these. Useful for restricted/ tailored/ even non-current distributions, and when you want to be sure that two or more installations are identical to one another in all respects. 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/