Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Tue, 28 Aug 2001 00:55:32 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: setup as a general purpose installer?
Message-ID: <20010828005532.A20867@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.21i

It is with gritted teeth that I ask this question:

Is anyone interested in discussing the issues in making setup
into a general purpose installer?

There are a few obvious issues in doing this.  I'm inclined to
think that we should be getting setup.exe to work better as
a cygwin installer rather than defocusing to ensure that it
can easily install packages from other projects.  Either that
or we scrap everything and move to rpm.

However, I actually, do have a need to be able to use setup.exe
internally at Red Hat with other "non-standard" mirror locations, so
if/when I implement that, part of the problem will be rectified.

Or, is it possible that by thinking more "globally" we might improve
setup.exe's robustness?

(I'm just grasping at straws really.  I've got very little interest
in improving setup.exe on these lines but that doesn't mean it's
not a good idea for someone else to take up)

cgf