Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <2C08D4EECBDED41184BB00D0B747334202FB439B@exchanger.cacheflow.com>
From: "Karr, David" <david DOT karr AT cacheflow DOT com>
To: "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
Subject: Storing a release/installation of Cygwin in a configuration manag
	ement system
Date: Thu, 10 May 2001 13:48:27 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"

It's very nice that Cygwin is constantly being improved.  You know that
every time you run "setup", you'll probably install some sort of
improvement.  However, when you start to think about maintaining a
"reproducible" development environment, you come to the conclusion that you
need to store a "snapshot" of the system, so new engineers can install
exactly the version of the development/build system that is supported.

What sort of things can I do to facilitate this?  I'd still like the ability
to update the "stored version" when I know there are changes I need, but in
general, I'd like the entire install package to be stored on our servers.

I guess there are options in "setup" for "install from local network" or
something like that.  It's possible that could be a part of the solution.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple