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 Message-Id: <5.2.0.9.2.20030227190011.029c5268@pop3.cris.com> X-Sender: rrschulz AT pop3 DOT cris DOT com Date: Thu, 27 Feb 2003 19:09:11 -0800 To: cygwin AT cygwin DOT com From: Randall R Schulz Subject: Re: setup dies on local install In-Reply-To: References: <5 DOT 2 DOT 0 DOT 9 DOT 2 DOT 20030227175924 DOT 029c4f18 AT pop3 DOT cris DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed At 18:27 2003-02-27, Igor Pechtchanski wrote: >On Thu, 27 Feb 2003, Randall R Schulz wrote: > > > [snip] > > > > This whole business comes under the "going against the grain" theme. > > You're going to have much better luck, far fewer headaches and keep you > > hair a lot longer if you do things the way they're intended to be done. > > Furthermore, you're going to be told that "rolling your own" > > installation procedure is not (kindly) supported here. > >Randall, > >I'm sorry, but this is not quite correct. The recent discussion about >"rolling your own" was not about an installation, but rather about >cygwin1.dll. Which would be expected to coexist with the "official" >cygwin1.dll. I think providing your own *mirrors*, whether in CD form or >on a network, is indeed encouraged. Anyone wanting to do that is directed >to read if they also >need to create a custom setup.ini file. > Igor Igor, I'm not sure I see how that follows. I was just responding to Steve's posting about the problems he had downloading and running Setup. Since he used the phrase "preserving the directory tree," I guessed that he did not use Setup to do the download. Since the directory layout created and required by Setup is not identical to that existing on the mirror from which the install tarballs are downloaded, one has to take extra steps (such as those in my shell script) to create that structure. Hence my hypothesis that he didn't properly recreate the required directory sturcture and my remarks that "rolling your own" is likely to cause one frustration. Steve's original post didn't mention cygwin1.dll at all, so I don't see how it goes to questions of which cygwin1.dll is used. Randall Schulz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/