Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <10d501c1aa95$3be4e470$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Michael Adler" <adler AT glimpser DOT org>, <cygwin AT cygwin DOT com>
References: <Pine DOT NEB DOT 4 DOT 44 DOT 0201311414380 DOT 27720-100000 AT reva DOT sixgirls DOT org>
Subject: Re: Scripting Installs? missing setup.hints
Date: Fri, 1 Feb 2002 07:24:06 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 31 Jan 2002 20:23:54.0705 (UTC) FILETIME=[3447BC10:01C1AA95]

----- Original Message -----
From: "Michael Adler" <adler AT glimpser DOT org>
> > It's part of the sources.redhat.com infrastructure.  It is in CVS
but it
> > is not intended for general use.  I don't know if it is even
available
> > for anonymous CVS access.
>
> Am I to assume that you're not interested in making that script
available?

It's been visible via CVS, see the cygwin-apps archive. It's *not
supported* though.

> > In case it isn't really clear, I'm not really interested in making
> > setup.exe a general purpose tool for you to use internally.  That
has
> > never been a goal, and I see nothing but headaches from moving in
that
> > direction.
>
> Granted, all that is clear to me. I appreciate that you're frank. Let
me
> try to ask again.
>
> I'm generating my own setup.ini since that's a good way to gain
control
> over what's being installed. I've written a program to handle this by
> integrating a stale version of a setup.ini from cygwin.com and some
> setup.hints. (ideally this would all come dynamically from
setup.hints)

You don't need to generate your own complete setup.ini. Use the latest
setup.exe snapshot (for now), and generate a 'merge' setup.ini that only
adds/changes any fields you care about. It's been designed to allow
corporate fiddles in that respect.

That said, I've no objection (heh, because I didn't write upset!) to it
floating about, but any questions on it's operation etc etc will be
offtopic here and in cyg-apps. The decision is Chris's 'cause it's his
script (I can only speak for setup.exe).

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/