This is the mail archive of the
mailing list for the Cygwin project.
RE: Seeking a suggestion for unattended mass install procedure
- From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr at ncbi dot nlm dot nih dot gov>
- To: "cygwin at cygwin dot com" <cygwin at cygwin dot com>
- Date: Mon, 4 Nov 2013 18:03:47 +0000
- 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> <5277DB67 dot 5050903 at cygwin dot com>
> Just make a list from that as part of your install script.
That is the problem, right there. I counted some 150 directories,
many of which contain 10+ packages, easily. A manageable install
command would have looked like "setup.exe -L directory -a" to
get and install everything it could have found under that directory,
rather than a command that spans two or more screen-fulls to list all
Any other alternative, please?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple