This is the mail archive of the
cygwin
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 19:04: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> <5F8AAC04F9616747BC4CC0E803D5907D0C40C962 at MLBXv04 dot nih dot gov> <5277E992 dot 8070602 at cygwin dot com>
> Are you saying this won't work?
> Or do you just not like it?
A little bit of both, actually. Windows CMD.EXE has an 8K limit on the command line
length, AFAICT. Even if that was not exceeded first time the package list
was created, it may easily get there on a complete re-run of the install procedure
(beginning with the manual package selection). The worst part is that it may
fail silently without setup even noticing until after the system is placed
into production (and failing because of the missing packages).
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