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:to:from:subject:date:message-id:references
	:mime-version:content-type; q=dns; s=default; b=t4hqYNGu9NONNqX3
	EDQunEHSnjTuOB+dpWFapkv4h3Tkg1o9SmbUlXq/Uep3gOnXv1Cm2vmnuk9amQ8m
	wST+hislOmbX2M8gtGyVC6CZFqI55COIyJ9Iwy8MDhIewJVmzaExq0/MeatPMGOI
	3j6EhIAIcQdVi3vebS/nWImNsUE=
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:to:from:subject:date:message-id:references
	:mime-version:content-type; s=default; bh=D7Ak13kR+Rlpln+zcf1KH/
	tcteI=; b=VRDhMS81WwdzP+gt+Vyz3oGJgO3omZSwDPXXjjOSgwJNUpzD9/Yb6n
	TNiaImm9wxUkUH/wSn/+8HYH1L+P+myxmRTZlckdHWWmoBnbc/aHjQnph33JOXfx
	cJqRbMQiKOvahu+liBRXBgBz6VneXM9LcOCUF87UGzhy1e/1pvBsc=
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=-0.1 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2
X-HELO: plane.gmane.org
To: cygwin AT cygwin DOT com
From: Achim Gratz <Stromeko AT nexgo DOT de>
Subject: Re: AdminCygwin Release
Date: Thu, 23 Jan 2014 18:15:04 +0100
Lines: 47
Message-ID: <87siseei1z.fsf@Rainer.invalid>
References: <CAO2ddnbtJ_mY1Yei6cx2GQO1dAWv=OV-cDVFO+aZD935MGQ7mA AT mail DOT gmail DOT com>	<52DEBB76 DOT 2040004 AT cygwin DOT com>	<CAO2ddnb+Vfn+199r-qqmPF=tL5XeEmYO2Qmn+=d2sKw4QK2Ong AT mail DOT gmail DOT com>	<52DEDDC5 DOT 2070703 AT cygwin DOT com>	<20140123021729 DOT GA31442 AT pixel DOT schutter DOT home>
Mime-Version: 1.0
Content-Type: text/plain
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
X-IsSubscribed: yes

Tom Schutter writes:
> 1) Modify cygwin_setup_config.bat to match your site requirements.
> 2) Copy cygwin_setup.bat and cygwin_setup_config.bat to a target host.
> 3) Run cygwin_setup.bat on the target host.
> 4) Repeat 2 and 3 on your other hosts.

I've been doing something very similar for a while now, with a few
modifications that mainly have to do with the fact that I can't expect
all hosts to have internet access and the requirement that an install,
update or re-install must be possible by executing a single executable
or script.

At the moment I'm working from a full internal mirror, but the plan is
to eventually download just those files that I will need to install
directly from an external mirror.  The required packages and the package
repos are listed in a setup.conf file.  This file has the information in
which order the package sources should be considered when multiple repos
offer the same package and finally the packages to install.  You can
also select test or prev versions on a per package basis or ignore named
packages from a certain package source.  You just need to list the
top-level packages (or entire categories if wanted), dependencies are
automatically pulled in.

Packages can be grouped into new categories, one of which will later be
used as the target for setup.exe to install (instead of listing the
individual packages).  From this I create a new setup.ini from the
contents of all package repos with just those packages that I need.
Lastly, all packages referenced by that setup.ini plus the install
scripts are copied to a software repository that all clients on the
network can access (it is also possible to put the whole thing on a USB
stick or DVD).

As in your scheme, since the actual install is done by setup.exe, the
resulting installation is indistinguishable from a "normal" Cygwin and
users familiar with setup.exe can modify package selections if they want
to as they are used to.  I consider this important and all the other
methods, some of which have been discussed in this thread, either don't
offer this possibility or require extra effort to maintain it.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables


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