To: cygwin@cygwin.com
From: Andrew Schulman <schulman.andrew@epamail.epa.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@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.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