X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
Date: Fri, 29 Jan 2010 14:11:07 +0100
Message-ID: <d37e30051001290511v4c7357f6sbdb1d620b7e99509@mail.gmail.com>
Subject: Putting a cygwin installation under bzr VCS ?
From: Jurgen Defurne <jurgen DOT defurne AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
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

Dear all,

I would like some input, thoughts really, about keeping a central
updated repository
with a Cygwin installation which can be updated by running bzr.

So, currently, I am testing cygwin 1.7 for deployment. However, the
deployment needs
to be done across 18 computers which are used as build servers. I know how to
download the packages and install them using a remote repository, but doing this
time and again on these systems is much work without value. Additionally, our
configuration needs to be spiced up with extra packages, like Perl
packages, mySQL
client library and other tools which are not found in the standard
Cygwin packages.

I have been using bzr already for over a year with other deployed
software (mostly
compilers) and I really haven't found any problems with it.

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 ?

Regards,

Jurgen

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