This is the mail archive of the
mailing list for the Cygwin project.
Re: Seeking a suggestion for unattended mass install procedure
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 04 Nov 2013 12:37:43 -0500
- Subject: Re: Seeking a suggestion for unattended mass install procedure
- Authentication-results: sourceware.org; auth=none
- References: <5F8AAC04F9616747BC4CC0E803D5907D0C40C86D at MLBXv04 dot nih dot gov> <5277D4A0 dot 1050809 at cygwin dot com> <5F8AAC04F9616747BC4CC0E803D5907D0C40C913 at MLBXv04 dot nih dot gov>
- Reply-to: cygwin at cygwin dot com
On 11/4/2013 12:22 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
Though I haven't experimented with this myself, I'd recommend looking at
using "setup*.exe" on the command line and listing the packages to install
Thanks. But I P.S.'d about that option as undesirable -- as it requires to
maintain quite a long list of packages, all listed individually...
Why do you need to maintain a list? You have the download directory, right?
Just make a list from that as part of your install script.
There are other, more esoteric ways to get "setup*.exe" to install a list
of packages but, in the end, it still requires a list of packages to know
what you want to install. So I don't see an advantage in these other
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple