This is the mail archive of the
mailing list for the Cygwin project.
Re: setup dies on local install
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Randall R Schulz <rrschulz at cris dot com>
- Cc: cygwin at cygwin dot com
- Date: Thu, 27 Feb 2003 22:45:11 -0500 (EST)
- Subject: Re: setup dies on local install
- Reply-to: cygwin at cygwin dot com
On Thu, 27 Feb 2003, Randall R Schulz wrote:
> 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.
> >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 <http://sources.redhat.com/cygwin-apps/setup.html> if they also
> >need to create a custom setup.ini file.
> > 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
Umm, yes, I can see that my post may be misinterpreted. I was responding
to your comment that "you're going to be told that "rolling your own"
installation procedure is not (kindly) supported here." I recall exactly
that (creating a local mirror/distribution) being suggested by prominent
project members (including Chris Faylor, IIRC). I understood that as an
encouragement to do so. Sorry for the ambiguity.
P.S. Cygwin developers are "just mean", so nothing is "kindly" supported
anyway, is it? ;-)
|\ _,,,---,,_ pechtcha at cs dot nyu dot edu
ZZZzz /,`.-'`' -. ;-;;,_ igor at watson dot ibm dot com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html