X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <4C49ED6A.4090902@bopp.net>
Date: Fri, 23 Jul 2010 14:28:42 -0500
From: Jeremy Bopp <jeremy AT bopp DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Standardizing a Cygwin installation across machines?
References: <D189CC2B-4453-4794-A386-5AD3B92D4011 AT anybill DOT com>
In-Reply-To: <D189CC2B-4453-4794-A386-5AD3B92D4011@anybill.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

On 7/23/2010 2:21 PM, John Cromartie wrote:
> Hi list,
> 
> I make heavy use of cygwin across multiple servers. It is used for build process automation and many other tasks. I would like to have a simple standard installation I can "roll out" to new systems, or even to just normalize existing systems. For example: I discover I need a new package to support some new endeavor that runs on four different servers.
> 
> Is there any way to do something like this?

Check out the command line options for setup.exe.  It will let you
update and add packages without user interaction if you like.  The only
problem is that you'll have to find some way outside of Cygwin to
automate running it remotely, if that's your idea.  If you try to update
Cygwin when there are running Cygwin processes, you'll find that any
file currently in use will not be replaced without a reboot.  Maybe you
could have a minimal installation installed somewhere else which is only
used to perform the updates on another installation.

Another option is to simply ZIP up the Cygwin installation and extract
that onto your target systems.  Again, you'll have to find some way to
automate this task outside the Cygwin installation being updated.
You'll also need to ensure that you use a Windows-native archive tool to
handle things if you're not using an alternative Cygwin installation to
perform the update.  Otherwise, things like symlinks will not be preserved.

-Jeremy

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