From: "Chris J. Breisch" <chris.ml@breisch.org>
To: cygwin@cygwin.com
Subject: Re: setup.exe different packages
Date: Wed, 29 Jan 2014 16:05:00 -0000 [thread overview]
Message-ID: <52E926B1.30804@breisch.org> (raw)
In-Reply-To: <loom.20140129T130612-117@post.gmane.org>
Achim Gratz wrote:
>
> They are, if you don't fiddle with a checkbox that you shouldn't be able to
> toggle in the first place. In other words it's a bug in the GUI that you
> are able to bypass the install of some Base packages.
>
No, I don't agree with that statement. I'd be more inclined to believe
that it's a bug in the command-line interface that doesn't allow you to
do what the GUI does.
The default installation package selected by the GUI is by no means a
minimally useful one, and there are many reasons why one might want to
install fewer packages than it includes. Being able to do so hardly
seems like a bug.
Frankly, I was surprised the dependency tree for bash was so large. Bash
depends on texinfo? I see the chain that gets you there, but it still
surprised me.
>
> Regards,
> Achim.
>
>
--
Chris J. Breisch
--
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:[~2014-01-29 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 14:41 BGINFO4X
2014-01-28 15:08 ` Marco Atzeri
[not found] ` <CAO2ddnY2UjXnqGJ0ve3bLkH4pctYK-2YdrO1jVpJEjnbYQHwCg@mail.gmail.com>
2014-01-28 17:18 ` BGINFO4X
2014-01-28 18:31 ` Achim Gratz
2014-01-29 9:19 ` BGINFO4X
2014-01-29 10:31 ` Chris J. Breisch
2014-01-29 10:46 ` BGINFO4X
2014-01-29 12:11 ` Achim Gratz
2014-01-29 16:05 ` Chris J. Breisch [this message]
2014-01-29 16:25 ` Achim Gratz
2014-01-29 16:39 ` Larry Hall (Cygwin)
2014-01-29 18:11 ` BGINFO4X
2014-01-29 19:58 ` Larry Hall (Cygwin)
2014-01-28 18:19 ` Chris J. Breisch
2014-02-01 11:57 ` Marco Atzeri
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=52E926B1.30804@breisch.org \
--to=chris.ml@breisch.org \
--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).