This is the mail archive of the
mailing list for the Cygwin project.
Re: How to detect a broken cygwin mirror? (gold star alert)
On Fri, 3 Sep 2004, Christopher Faylor wrote:
> On Fri, Sep 03, 2004 at 01:49:40PM +0100, Dave Korn wrote:
> >> -----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
> Can I get YA gold star for Dave here?
> This is eminently sensible advice. I was thinking the same thing but
> every message I started to compose on the subject did not put it as well
> or as non-meanly.
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Happiness lies in being privileged to work hard for long hours in doing
whatever you think is worth doing." -- Dr. Jubal Harshaw
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html