public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Dr Rainer Woitok <rainer.woitok@gmail.com>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Running Cygwin's "setup.exe" on a new computer
Date: Wed, 02 Sep 2015 10:54:00 -0000	[thread overview]
Message-ID: <21990.54586.643600.292606@woitok.gmail.com> (raw)
In-Reply-To: Msg <55E5AEAF.1080103@gmail.com> of 2015-09-01 15:57:03 +0200 from marco.atzeri@gmail.com

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.

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?

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

  reply	other threads:[~2015-09-02 10:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 12:50 Dr Rainer Woitok
2015-09-01 13:57 ` Marco Atzeri
2015-09-02 10:54   ` Dr Rainer Woitok [this message]
2015-09-02 12:06     ` Marco Atzeri
2015-09-03 14:24       ` Warren Young
2015-09-02  7:17 ` Achim Gratz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21990.54586.643600.292606@woitok.gmail.com \
    --to=rainer.woitok@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).