public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Adam Puckett <adotsdothmusic@gmail.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: tip for blind users of setup.exe regarding package installation
Date: Wed, 07 Mar 2012 01:55:00 -0000	[thread overview]
Message-ID: <CAK1FW3VXcb0nB0W8XDZG_CHVn-PH=Nz0Z0E-ph+7woDjFkgP6Q@mail.gmail.com> (raw)
In-Reply-To: <0105D5C1E0353146B1B222348B0411A20A5C2A9388@NIHMLBX02.nih.gov>

I put it here to avoid being told to TITTTL.

On 3/6/12, Buchbinder, Barry (NIH/NIAID) [E] <BBuchbinder@niaid.nih.gov> wrote:
> Adam Puckett sent the following at Monday, March 05, 2012 10:59 AM
>>
>>Here's how I went about installing Cygwin via setup.exe with the free,
>>open source screen reader NVDA:
>>
>>1. Download and run setup.exe, and click "Next" at each prompt, as the
>>user guide says, for a core install.
>>2. Install additional packages with the -P option. E.G.:
>>
>>setup -P gcc -P git -P bzr -P python
>>
>>etc.
>
> (1) Shouldn't this have been appropriate for the main list, not talk?
>
> (2) This sounds like it might work as a basic for the generic "automatic
> install" question that periodically shows up on the main list.  Might it
> be appropriate for a FAQ or somewhere else in the documentation or on the
> web site?  (Not that I have tried this or that it matters to me.)
>
> - Barry
>   Disclaimer: Statements made herein are not made on behalf of NIAID.
>
>

  reply	other threads:[~2012-03-07  1:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-07  1:11 Buchbinder, Barry (NIH/NIAID) [E]
2012-03-07  1:55 ` Adam Puckett [this message]
2012-03-07  3:45   ` Christopher Faylor
  -- strict thread matches above, loose matches on Subject: below --
2012-03-07 11:12 Buchbinder, Barry (NIH/NIAID) [E]
2012-03-07 11:21 ` Corinna Vinschen
2012-03-07 15:23 ` Christopher Faylor
2012-03-07 20:36   ` Adam Puckett
2012-03-05 15:58 Adam Puckett

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='CAK1FW3VXcb0nB0W8XDZG_CHVn-PH=Nz0Z0E-ph+7woDjFkgP6Q@mail.gmail.com' \
    --to=adotsdothmusic@gmail.com \
    --cc=cygwin-talk@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).