public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Seeking a suggestion for unattended mass install procedure
Date: Mon, 04 Nov 2013 19:28:00 -0000	[thread overview]
Message-ID: <5277F52F.4020709@cygwin.com> (raw)
In-Reply-To: <5F8AAC04F9616747BC4CC0E803D5907D0C40CA72@MLBXv04.nih.gov>

On 11/4/2013 2:11 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> Alternatively, you can grab the sources for setup and add an option
> to do what you want the way you want it.
>
> Well, that's a trivial option with open source, of course.  But also
> it means to maintain a branch of our own setup.exe, which is the
> least favorable of all.

That's the glass half-full view of it. ;-)

Assuming what you come up with is not just specific to your needs, I
see no reason the new option couldn't be included into setup's sources.
After all, I believe that's the ideal option that you were hoping for
(but already knew didn't really exist) when you asked the question.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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 19:28 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
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) [this message]
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=5277F52F.4020709@cygwin.com \
    --to=reply-to-list-only-lh@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).