Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Thu, 27 Apr 2000 00:08:17 -0400
Message-Id: <200004270408.AAA12994@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <20000426234810.A29028@cygnus.com> (message from Chris Faylor on
	Wed, 26 Apr 2000 23:48:10 -0400)
Subject: Re: setup issues
References:  <20000426234810 DOT A29028 AT cygnus DOT com>


> I think that we will always have issues with proxies, firewalls, etc.
> setup.exe goes out of its way to do the right thing with these but
> if the system is misconfigured in some way, it will still fail.

If so, they can't visit the web site or download setup.exe either.  We
must be doing something different than IE if IE can see out but
setup.exe can't.  It's a bug.

> I think the simplest workaround for this would be to rename all of the
> binary .tar.gz files, from foo.tar.gz to foo-bin.tar.gz.  I assume that
> most ftp clients would be able to do something like mget */*-bin.tar.gz

That won't work if we store multiple versions, which I think we should
allow for.  Better, a separate subdir of symbolic links of "everything
you need", that setup either uses or knows to ignore.

> Then, when someone has a problem we just have to tell them to download
> setup.exe and all of the above files and then run setup.

The behemoth setup.exe (full.exe?) is a better idea.  We just have to
automate building it (a setup.exe option? ;)