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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Question about old win32 api
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>	<CAOC2fq8odvsRD3hmkHivuTvNw3CLR6sHJyKhMyrOqP0n=gdeww@mail.gmail.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
Content-Type: text/plain

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