DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type
	:content-transfer-encoding; q=dns; s=default; b=JRzKnLTLhcYnHU6X
	Rb2cO0FOcBNRBqulcDGabBiKz+kYtcTh+IoR/jDQ0rAg+a/PUBid7TlEFFagoQZs
	RyCQINjHTjRVHYTW/ZRZFNhSwpEehPo0wa+hyc3Q/DKWK3N+NQow99CxrZR8ph8s
	+YqJGwNUO4+10FPZlefhBzJynG0=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <684FB57D-F0F8-4BB9-AB72-7D58F91FEFE9@solidrocksystems.com>
References: <A8FCEC4C682E094AAB49CE0CE41E28EA18502B88@EXCHMB06.is.l-3com.com>	<1442854377.11704.18.camel@cygwin.com>	<A8FCEC4C682E094AAB49CE0CE41E28EA18502C2E@EXCHMB06.is.l-3com.com>	<1195136399.20150921222509@yandex.ru>	<CAOC2fq-WaBg1aug_iG92Z3B7PvYD+EmpsWhCdS7HHDW0JZMijQ@mail.gmail.com>	<5600691F.2090204@gmail.com>	<CAOC2fq8XD9kx8VbVoWf0pZ3+iX5Xp-Sx18mabnn75WwKkAVwVw@mail.gmail.com>	<C4D33CAB-A685-45B6-B970-0328B58869E2@solidrocksystems.com>	<CAOC2fq_Qsq4CLv2Oc3f797JZCrANBqyY_RsgGbLVjT0+RaJ4eQ@mail.gmail.com>	<684FB57D-F0F8-4BB9-AB72-7D58F91FEFE9@solidrocksystems.com>
Date: Tue, 22 Sep 2015 10:16:21 -0700
Message-ID: <CAOC2fq8odvsRD3hmkHivuTvNw3CLR6sHJyKhMyrOqP0n=gdeww@mail.gmail.com>
Subject: Re: Question about old win32 api
From: Michael Enright <mike@kmcardiff.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On Mon, Sep 21, 2015 at 9:16 PM, Vince Rice  wrote:
>
> The blindness was, as I’ve already pointed out, caused by blindly
> updating software

No one was "updating"! I have diagnosed what I did "wrong" before and
I am satisfied with my conclusion. I don't yet know of a way to keep
changes from affecting me, but I know some things I can do to be
prepared for the changes that might happen, so I'm doing those things.

No one was updating. New workers needed new Windows boxes with Cygwin
on them. What is the process for putting Cygwin on a new Windows box?
It isn't "rsync Cygwin from IT".

Cygwin's default (or only) distribution method has a role to play in
this. Does anyone ever setup Cygwin on a new Windows install other
than by downloading setup_x86.exe or setup_x86-64.exe and working from
there? Is any such alternative given equal priority on cygwin.com ?

I am interested to hear if anyone has managed a group of Cygwin users
and the configuration they use, and how they went about it.

More out there, I'm interested in thoughts about making it possible to
tell a group such as a customer base (a group of autonomous,
free-will-possessing individual organizations) how to setup Cygwin so
a non-Cygwin component can be added on top and work even though it
might not still work with a regular default fresh Cygwin.

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