X-Recipient: archive-cygwin@delorie.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:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=HAkoaOQNG9c1R4E885+VnVpfH9Mou
	5goxMLUoToN5JOspcvnS3T3BYStaoFWLpekJxquKAKKksvvv0qPSKDvDfIPGEUeI
	OxYuCnznMf4q0pwstzdJQjTuvrcBdOOa2cPMcruLp3B8+StOuMfYQ+lbWxqZ3MSG
	U+t+FbjypI6MKw=
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:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=vX5EHtYBYYdG3hAf3iFx7t26ksM=; b=tOz
	K62M3u+R9JLO8keypJ1o6lyoUeg39lcDNS+ilinCm1HZ6aLQM2sZ+bpRTkTGsYMQ
	d+COx6O6msWV8n5AE504CPMzQpeW56TgZgGnEctujuR0sxK8v7YDg6urL6LBpb5K
	2WRbpnc+zodIzwj9m2rCFkge1uaW7BuXVMVi5nvg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.3 required=5.0 tests=AWL,BAYES_60,RDNS_NONE,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2
X-HELO: nihxway6out.hub.nih.gov
X-IronPortListener: Outbound_SMTP
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0GAMT5d1KcKEfa/2dsb2JhbABZgweBC78/gSsWbQeCJQEBAQMBEihECwIBCA0VFBAfEyUCBBsah1kGogmcTI8nOIMggQ4DjlSQGoslgyaCKg
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Seeking a suggestion for unattended mass install procedure
Date: Mon, 4 Nov 2013 19:51:23 +0000
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C40CB1E@MLBXv04.nih.gov>
References: <5F8AAC04F9616747BC4CC0E803D5907D0C40C86D@MLBXv04.nih.gov> <5277D4A0.1050809@cygwin.com> <5F8AAC04F9616747BC4CC0E803D5907D0C40C913@MLBXv04.nih.gov> <5277DB67.5050903@cygwin.com> <5F8AAC04F9616747BC4CC0E803D5907D0C40C962@MLBXv04.nih.gov> <5277E992.8070602@cygwin.com> <5F8AAC04F9616747BC4CC0E803D5907D0C40CA43@MLBXv04.nih.gov> <5277F460.3070205@cygwin.com>
In-Reply-To: <5277F460.3070205@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id rA4JqnIR003352

> you're adding additional requirements

Rather revealing them...

The procedure is still to grab the current setup, make package selection,
download with satisfying the dependencies, then install on a bunch of
boxes in the batch mode, unattended.

When a new set of machines is to be built, repeat the procedure with
then-current CYGWIN, possibly starting with the package selection step
(if needed -- i.e. the package requirements have changed, some requested
to be added / removed)...

I think I've got enough information to relay to our Systems group
and see what they say.

Thanks everybody (including Marco, Achim, and cfg) who responded!

Anton Lavrentiev
Contractor NIH/NLM/NCBI


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


