Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From:	"Dave Korn" <dk AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: How to detect a broken Cygwin mirror?
Date:	Fri, 3 Sep 2004 13:49:40 +0100
MIME-Version:	1.0
In-Reply-To:	<20040903014127.6FBDC8454B@pessard.research.canon.com.au>
Message-ID:	<NUTMEGVNBGmfO09UtHe00001136@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime:	03 Sep 2004 12:49:40.0937 (UTC) FILETIME=[7A8C4390:01C491B4]

> -----Original Message-----
> From: cygwin-owner On Behalf Of luke.kendall
> Sent: 03 September 2004 02:41

> Cygwin-specific expertise, and move on.  The worst experiences, in my
> opinion, are like this one, that seem to come down to a broken mirror:
> our mirror rsyncing to it and breaking, and then people updating or
> installing from our broken mirror, and getting into states 
> like my PC is
> in now.

  I don't think it's a sensible policy to be permanently chasing the
bleeding-edge of development in a production environment.  I think you
should set up your mirror with known good and stable versions of the tools
you need in your environment and then freeze it, and only update parts of it
as and when specifically needed and after testing and change control.  IOW,
I think this problem is better solved by development methodology and
management techniques than by a shell script.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -