Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <425FBC48.1070408@ieee.org>
Date: Fri, 15 Apr 2005 14:06:16 +0100
From: Jason Pearce <jason DOT pearce AT ieee DOT org>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: Cygwin List <cygwin AT cygwin DOT com>
CC: Carl Perry <cperry AT ticom-geo DOT com>
Subject: Re: Building a common cygwin enviroment for network distribution
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

> I've looked around the Cygwin site for information on installation 
> that doesn't use the supplied setup.exe, and I've found a lot of "you 
> on your own" so I'm hoping to get some help here.  Thanks! 

What so wrong with setup.exe?

I am doing a similar cygwin roll out at my work site and I use 
setup.exe. It can be run with command line switches so that it does not 
prompt the user and installs/updates automatically. Then you just define 
you own custom package, add it to Base group and make it depend on all 
the pacakges you want installed by default.
See http://sources.redhat.com/cygwin-apps/package-server.html

By staying with setup.exe your installation process will update as 
Cygwin does.

Jason


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/