public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Seeking a suggestion for unattended mass install procedure
Date: Mon, 04 Nov 2013 16:27:00 -0000	[thread overview]
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C40C86D@MLBXv04.nih.gov> (raw)

Hello All,

I am trying to help my site's Systems team to straighten up CYGWIN
installation process, which they will need to perform to build new
PCs, and I have volunteered to ask on their behalf here..

As far as they can tell, there is no such an installation option that
tells to install "everything from the download directory".  What they
do is that they run setup.exe to manually check everything from the available
packages that they want to have installed on a PC, then they follow the option
to download any left-over package dependencies, from which step setup.exe takes
control and downloads / installs the selections.

Now, they want to replay the setup unattended with using only those downloaded
packages again, on any other new PC, without going through the selection process
again, so basically to install everything that setup.exe has already
_downloaded_ to a certain directory when run manually (where all the
dependencies have already been satisfied, so the set is self-sufficient).

How / Whether can they do such an install?

Thanks,

Anton Lavrentiev
Contractor NIH/NLM/NCBI

P.S. There is an option for setup.exe to list all wanted packages,
but the actual list appears to be very long, so they want to avoid
using it, if possible.


--
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:[~2013-11-04 16:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04 16:27 Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2013-11-04 17:09 ` Larry Hall (Cygwin)
2013-11-04 17:22   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-04 17:37     ` Larry Hall (Cygwin)
2013-11-04 18:03       ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-04 18:17         ` Eric Lilja
2013-11-04 18:27           ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-04 18:32             ` Christopher Faylor
2013-11-04 19:35             ` Achim Gratz
2013-11-04 20:14             ` Buchbinder, Barry (NIH/NIAID) [E]
2013-11-04 20:31               ` Christopher Faylor
2013-11-04 18:38         ` Larry Hall (Cygwin)
2013-11-04 19:05           ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-04 19:25             ` Larry Hall (Cygwin)
2013-11-04 19:52               ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-04 19:11           ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-04 19:28             ` Larry Hall (Cygwin)
2013-11-04 19:33             ` Christopher Faylor
2013-11-04 19:40             ` Achim Gratz
2013-11-04 18:50         ` marco atzeri
2013-11-04 19:28           ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-04 20:24             ` marco atzeri
2013-11-04 19:29 ` Achim Gratz
2013-11-07  5:02 Buchbinder, Barry (NIH/NIAID) [E]
2013-11-07 15:06 ` Mikhail Usenko

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=5F8AAC04F9616747BC4CC0E803D5907D0C40C86D@MLBXv04.nih.gov \
    --to=lavr@ncbi.nlm.nih.gov \
    --cc=cygwin@cygwin.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).