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
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Sat, 22 Apr 2000 12:13:46 -0400
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Two complaints about lack of massive setup.exe
Message-ID: <20000422121346.A1589@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To: cgf AT cygnus DOT com, cygwin-developers AT sourceware DOT cygnus DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.1.8i

We've had two complaints that people miss the old setup.exe that worked
"so well".

It would be pretty trivial (thanks to Ron's excellent design) to have
the current setup.exe pull in all of the non-source tar files and
extract them.  It would be a huge binary, but if that's what people
what...

Of course, the next request would be for a split up setup.exe which
would be easily downloadable.  I don't think we want to go that route.

As an alternative, maybe we could provide a mechanism for people to
easily download the individual tar files.  One problem that I see now
is that you can't just say something like:

ftp sourceware.cygnus.com
cd /pub/cygwin/latest
mget */*.tar.gz

since that will download the sources too.

So, I'm proposing two things:

1) Autogenerate (via a cron job) a fullsetup.exe automatically
   when the contents of a binary tar file in a subdirectory is
   updated.  This would possibly require placing some cross build
   tools (linker, libraries, etc.) on sourceware

2) Differentiate the "binary" tar files in some way that will make
   them easily selectable.  One easy way to do this would be to
   move all of the source tar files out of latest and create a latest-src
   directory.  This would make everything transparent but I don't know
   about maintaining two parallel directories.

   The other method would be to add a -bin to all of the binary tar files.
   I don't think that this would even require a change to setup.c but I
   don't know for sure.

Comments?

cgf