X-Recipient: archive-cygwin AT delorie DOT com
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=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=g3nHTVDMV0KWpbLawr0GEr
	gvBw4=; b=R5WvxmaHsCk4wZa3Cwd22YDdD9je1+HpiVpk/RYAKfNyk4iFSie6z0
	qVo0yz9Bqw8EJFGoccpcHvpKfkjYJKxL9sGGsS4cd+jDwnqtdxLehgwkpxNqMRg8
	otVU0s6UYvar9UQc4caPGs56yVcV+E8tMSUcnX57WR4KlrWcBfmZc=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-yk0-f170.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:date         :message-id:subject:from:to:content-type:content-transfer-encoding;        bh=sJ+KhKbcdm3SegnFz3RFGAGn1UpWKjASuAPTmyvZnws=;        b=Y7UFbB50VuFJNLpSpvc+72FtdJOVzHPeBtGACA2EwWh7SmP8fvRJNSedObHFFHFLKA         HhJ9/uLJUrfvD+M8abQiarwYCmTXblf3ayVJ0E5QU2DgZ2aDMsEWRjY/i0al3vaS0sa6         G/2llULPFBvMNBcSHrC9fqmXND0XsrH+2YOVOEdQFPWj233hWb/UiebQxsHRb4l1Vxda         rwI/aVfJDjWpqtosgsQep1kX64Gn7iYjZC73YZ9B0KxbxxgY1mo/116zO9/DThiw+3oU         ceWdGJDYPi5AtRx50qGxiTdTUE65y0sJXnPNVnQ/CKIKDZCDCu0EbWy8ndZ5UM4ZaZJg         Ae8A==
X-Gm-Message-State: ALoCoQllMEBl5wxjyjfgaoevO6LYREUZWY771YFOXkSNMvQSAuXbrUrFjgBLFu509wfv7xpHoIkr
MIME-Version: 1.0
X-Received: by 10.13.202.70 with SMTP id m67mr21129926ywd.45.1442942181439; Tue, 22 Sep 2015 10:16:21 -0700 (PDT)
In-Reply-To: <684FB57D-F0F8-4BB9-AB72-7D58F91FEFE9@solidrocksystems.com>
References: <A8FCEC4C682E094AAB49CE0CE41E28EA18502B88 AT EXCHMB06 DOT is DOT l-3com DOT com>	<1442854377 DOT 11704 DOT 18 DOT camel AT cygwin DOT com>	<A8FCEC4C682E094AAB49CE0CE41E28EA18502C2E AT EXCHMB06 DOT is DOT l-3com DOT com>	<1195136399 DOT 20150921222509 AT yandex DOT ru>	<CAOC2fq-WaBg1aug_iG92Z3B7PvYD+EmpsWhCdS7HHDW0JZMijQ AT mail DOT gmail DOT com>	<5600691F DOT 2090204 AT gmail DOT com>	<CAOC2fq8XD9kx8VbVoWf0pZ3+iX5Xp-Sx18mabnn75WwKkAVwVw AT mail DOT gmail DOT com>	<C4D33CAB-A685-45B6-B970-0328B58869E2 AT solidrocksystems DOT com>	<CAOC2fq_Qsq4CLv2Oc3f797JZCrANBqyY_RsgGbLVjT0+RaJ4eQ AT mail DOT gmail DOT com>	<684FB57D-F0F8-4BB9-AB72-7D58F91FEFE9 AT solidrocksystems DOT 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 AT kmcardiff DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t8MHGevF007944

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