This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Running Cygwin's "setup.exe" on a new computer
- From: Marco Atzeri <marco dot atzeri at gmail dot com>
- To: Dr Rainer Woitok <rainer dot woitok at gmail dot com>
- Cc: cygwin at cygwin dot com
- Date: Wed, 2 Sep 2015 14:06:22 +0200
- Subject: Re: Running Cygwin's "setup.exe" on a new computer
- Authentication-results: sourceware.org; auth=none
- References: <21989 dot 40723 dot 827300 dot 907850 at woitok dot gmail dot com> <55E5AEAF dot 1080103 at gmail dot com> <21990 dot 54586 dot 643600 dot 292606 at woitok dot gmail dot com>
On 02/09/2015 12:53, Dr Rainer Woitok wrote:
Marco,
On Tuesday, 2015-09-01 15:57:03 +0200, you wrote:
...
$ cygcheck -cd | awk 'BEGIN{printf("setup-x86_64.exe ")} {if (NR>2) {
printf ("-P " $1 " ") }} END { printf ("\r\n pause ")}' > cyg-install-x86_64.bat
Even if I slightly compress the command line created that way by using a
single "-P" option followed by the string of comma separated package
names, I end up with a command line consisting of some 16700 characters!
I'm not at all sure how Windows and/or "setup-x86*.exe" would react to
that.
My W7 64bit had no complain for 23004 byte line
;-)
Besides, since "cygcheck" apparently finds the relevant information in
some file, and "setup-x86*.exe" apparently finds the relevant informat-
ion in some file, too, it would perhaps be way easier to just provide
the correct file in the correct location on the new machine.
Any ideas along these lines, anybody?
https://cygwin.com/ml/cygwin/2015-09/msg00023.html
Sincerely,
Rainer
--
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