Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <0ba101c1a999$b639db60$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Wayne Willcox" <wayne@reliant.immure.com>,
   "Randall R Schulz" <rrschulz@cris.com>
Cc: <cygwin@cygwin.com>
References: <20020129165825.GC641@redhat.com> <5.1.0.14.0.20020129114033.00b1f148@mail.corp.lumeta.com> <5.1.0.14.0.20020129114033.00b1f148@mail.corp.lumeta.com> <5.1.0.14.0.20020129120453.022a5068@mail.corp.lumeta.com> <5.1.0.14.2.20020129092834.02450008@pop3.cris.com> <20020129140450.A89307@reliant.immure.com>
Subject: Re: Scripting Installs?
Date: Thu, 31 Jan 2002 01:23:38 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


===
----- Original Message -----
From: "wayne" <wayne@reliant.immure.com>

> By the way I do write tools using some of cygwin and I am regularly
> asked if there is someway  to just point and click to install
> just what they need.  They don't know exactly what my tools require
> so they can't select just the parts required.  Now I can and do
> tell them but it would be easier for me and them if there was a way
for
> me to ease their install efforts.  This would go a long way to
> convincing my company to migrate.

Here's how:
Use the latest setup.exe snapshot, or the setup.exe being released
real-soon-now.
Create a setup.ini on a local web server describing your software. Read
http://www.cygwin.com/setup.html. Add the appropriate requires: line to
your local setup, which will drag in the needed packages from the normal
cygwin mirror sites.

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/