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 Date: Thu, 13 Oct 2005 10:31:47 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: Why is setup.exe so difficult? Am I missing something? In-Reply-To: <434DF431.D3CCEE18@dessent.net> Message-ID: References: <6 DOT 1 DOT 2 DOT 0 DOT 2 DOT 20051012083603 DOT 0485aec0 AT 127 DOT 0 DOT 0 DOT 1> <434D8C40 DOT 23A2EC31 AT dessent DOT net> <20051012224046 DOT GA30149 AT trixie DOT casa DOT cgf DOT cx> <434DCEF7 DOT 9060801 AT zedasoft DOT com> <20051013050356 DOT GD30149 AT trixie DOT casa DOT cgf DOT cx> <434DF431 DOT D3CCEE18 AT dessent DOT net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wed, 12 Oct 2005, Brian Dessent wrote: > Christopher Faylor wrote: > > > The 'now-abandoned "install it all at once"' problem was unabandoned two > > setup releases ago (I believe), recent advice notwithstanding. Maybe > > the setup developers will correct me if I'm wrong but AFAIK, there is no > > longer any reason to split a cygwin install into two. > > The original reason for the advice was because there was a handle leak, > which caused problems if setup tried to extract from a large number of > .tar.bz2s in one session. That has been corrected (I think?) and so in > theory it should no longer matter. FWIW, I haven't had any problems with rather complex (i.e., much larger than "base") installs with recent setup versions. I haven't tried the full install. > It's possible that there is still something wacked in the postinstall > ordering that would cause errors if you tried to go from zero to every > available package in one go. I'll have to try that scenario and see if > I can make it happen. Though AFAIK it should run them in dependency > order and work fine. > > Brian No, until is applied, setup will run postinstall scripts in alphabetical order. > (It's unfortunate that most of the sentences above are "in theory" and > "I think". I would like to say for sure that it should work, but it's > not something that I've personally done that often because to be honest > I really loathe the idea that one would have to install all 2.4GB of > stuff just because one didn't know what was required.) It should be reasonably easy to add a dialog box that asks such people "Are you SURE you want to install EVERYTHING? That's 2.4GB!". That ought to discourage superfluous full installs. The number in the box could be easily computed from setup.ini. However, I've suggested previously to create a few "installation profiles" (e.g., "development", that includes "make", "gcc", "vi", etc, or "maintainer development", which also adds the autotools). I'm not volunteering to implement this, as I'm devoting my time to a new UI, but it shouldn't be particularly hard -- these "profiles" sound like simple "sets of package names". Initially, they may even duplicate information (so, the "maintainer development" example profile above will include all the packages from the "development" profile, instead of having a dependence on it). This looks sufficiently decoupled from the setup versioning and package selection logic that it doesn't require very deep knowledge of it, and is a good exercise to gain more such knowledge. Any takers? Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. /DA -- 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/