X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.3 required=5.0 	tests=AWL,BAYES_50,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew Schulman <schulman DOT andrew AT epamail DOT epa DOT gov>
Subject: Re: Putting a cygwin installation under bzr VCS ?
Date: Mon, 01 Feb 2010 09:18:45 -0500
Lines: 15
Message-ID: <tcodm5t84c4haa8jvbv75v2bkvl7e45n1o@4ax.com>
References: <d37e30051001290511v4c7357f6sbdb1d620b7e99509 AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Archive: encrypt
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

> So, what do you think about putting one standard installation under
> bzr (Windows)
> control and then pulling in changes from the different PC's when they are ready
> for it ?

That seems like a workable approach.  A disadvantage is that by putting all
of those binaries into bzr, you'd get a large .bzr directory, with all of
the previous versions of every binary.  However, that would only be true on
the master host.  On the slave hosts you could use lightweight checkouts
and so not take up all of the extra space there for history.

A lighter-weight approach would be to use rsync or unison instead, to
synchronize the satellite hosts to the master.  That would avoid the space
and work overhead of keeping the version control history, but you'd lose
the ability to roll back changes if for some reason they created problems.


--
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