Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <106401c1aa8f$1f185c60$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin@cygwin.com>, "Randall R Schulz" <rrschulz@cris.com>
References: <20020131183628.28860.qmail@web14205.mail.yahoo.com> <5.1.0.14.2.20020131112750.022c6b68@pop3.cris.com>
Subject: Re: setting up cygwin
Date: Fri, 1 Feb 2002 06:40:21 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Randall R Schulz" <rrschulz@cris.com>


> Rob,
>
> Setup.exe serves the purpose of mirroring just fine, as along as all
you
> want to mirror is a set of Cygwin install packages, with or without
source
> (or, for that matter, with the current version of Setup.exe, source
alone).

Randall, there is a difference between being able to use a tool for
something, and it being designed for something.

Being the setup maintainer, I think I am in the position of being able
to state it's design parameters!

I repeat: Setup is not designed for mirroring, and if one wants to grab
all the binaries, and all the sources, then one should use a mirroring
tool.

I've no objection to a second .exe being built leveraging the setup.exe
source, in the cinstall directory that *is* designed for mirroring, but
I am not going to try to make setup.exe a mirror tool for cygwin! The
reasons have already been stated, both here and on cygwin-apps.

Rob


--
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/