From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Seeking a suggestion for unattended mass install procedure
Date: Mon, 04 Nov 2013 18:32:00 -0000 [thread overview]
Message-ID: <20131104183237.GE5526@ednor.casa.cgf.cx> (raw)
In-Reply-To: <5F8AAC04F9616747BC4CC0E803D5907D0C40C9B3@MLBXv04.nih.gov>
On Mon, Nov 04, 2013 at 06:27:48PM +0000, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> I have an install script for Cygwin. It's not offline
>
>Thanks for the suggestion. My Systems team need to install from scratch
>on bare boxes, from only an image DVD (which contained all the requisites of
>the future machine, including CYGWIN's setup and the downloaded directory,
>as I previously described).
>
From the replies I've got so far, I beginning to think it's close to impossible
>without having to list (all) the packages...
I don't understand your objection to generating a script which lists all
of the packages that you want to install. Obviously you wouldn't expect
the user to do that. You'd just create a .bat file to do this.
Alternately, maybe you could get away with just changing all of the
"requires: " in setup.ini for the packages that you are interested in to
"base".
This is not an insurmountable problem. It just takes some scripting.
cgf
--
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
next prev parent reply other threads:[~2013-11-04 18:32 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]
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 [this message]
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=20131104183237.GE5526@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--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).