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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=fe9qg
	gMJlPhNI1cUuG8qOjKbhmJK6R+CU2kyQyZvR6V8YZ4gHO7QPYHW7pygewJ9ZwTXF
	uk47nVmRo3gFXoqSkiQFNCWZyAYiFWkL4rQlGm6Yl4oSxhjOx1bkIr+ajkMWiy0O
	Oux/J/9byRAg/gDTfGwy3hK97f9Ob/NH/6ak6c=
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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; s=default; bh=0UJPBHrXJgn
	T098xArQiEASi5qs=; b=FHOdAw6vFLNH5BE4Vjr8LTHqMa+M2dgegv44beVl8KJ
	YqMwy/4a8tpiaG8wei0JTzoT8udQwTCfgi7E09TJJ+tepctdkvsLwUR/41tdDqt1
	rAbJLD40mUMchox1+Xbaisop+LXZtDoEC5HKWHOjaCB/h2KvuOiil7b5kmvAmSP8
	=
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.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-in-16.arcor-online.net
X-DKIM:	Sendmail DKIM Filter v2.8.2 mail-in-15.arcor-online.net 3nLB5Y5vcTzB5wP
From:	Achim Gratz <Stromeko AT nexgo DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: Question about old win32 api
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> <CAOC2fq8odvsRD3hmkHivuTvNw3CLR6sHJyKhMyrOqP0n=gdeww AT mail DOT gmail DOT com>
Date:	Tue, 22 Sep 2015 20:30:25 +0200
In-Reply-To:	<CAOC2fq8odvsRD3hmkHivuTvNw3CLR6sHJyKhMyrOqP0n=gdeww@mail.gmail.com> (Michael Enright's message of "Tue, 22 Sep 2015 10:16:21 -0700")
Message-ID:	<87eghqgvcu.fsf@Rainer.invalid>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)
MIME-Version:	1.0

Michael Enright writes:
> 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.

I do and the only sane way is to have a local mirror with exactly the
packages and versions that you are going to install and your own
setup.ini.  I integrate Cygwin upstream, Cygwin Ports plus literally
hundreds of locally built packages via some scripting.  In principle
it's possible to provide multiple versions (e.g. for staged rollouts) by
having separate setup.ini files, but there's no automation for keeping
the mirror in sync at the moment.  I also compile setup.exe myself
(although at the moment I have no patches on top of upstream).  There's
a wrapper script around setup that will install the correct variant of
Cygwin initially and keep it updated later.

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

You could replace the Cygwin key in setup.exe with your own, remove the
ability to install without the signature check and sign your setup.ini;
that should take care of any inadvertent use of the "wrong" Cygwin.
I've not done that yet, but eventually will so the installations can not
be manipulated without some real effort, even inadvertently.  If the
users still get themselves into trouble, then it's their problem, not
yours.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

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

- Raw text -