From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: cmp missing from base
Date: Mon, 09 May 2016 15:16:00 -0000 [thread overview]
Message-ID: <741009F0-E57D-44DA-B728-68BDB4486DDD@etr-usa.com> (raw)
In-Reply-To: <572D891C.2040002@towo.net>
On May 7, 2016, at 12:20 AM, Thomas Wolff <towo@towo.net> wrote:
>
> Am 07.05.2016 um 03:41 schrieb Warren Young:
>> On May 6, 2016, at 3:53 AM, Thomas Wolff <towo@towo.net> wrote:
>>> after a recent fresh installation of cygwin, I was surprised that `cmp` was missing, which is part of the traditional Unix base commands.
>>> I think the diffutils package should be part of the base installation.
>> We’ve never really had a hard rule on what is in Base and what isn’t. It’s always been a judgement call.
>>
>> I wonder if the rule should just be “POSIX”?
Over the weekend, I realized that the rule can’t be that simple, because that would drag in GCC.
> maybe there can be a guideline, and more a guideline of common practice than of a 15th standard.
The problem, of course, is that there is no common practice.
I think the closest parallel to the Cygwin Base philosophy is the minimal or base installs of several other *ixes, particularly the BSDs. It is also something like a throwback to the SysV Unixes, prior to about 1992, when you could count on things like X and the C compiler to be separate installs.
But even that guideline isn’t especially useful, since often such OSes *do* include the C compiler and all its support tooling.
Ultimately, I think Cygwin Base is whatever Corinna and Yaakov say it is. :)
--
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:[~2016-05-09 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <572C697E.1090408@towo.net>
2016-05-07 1:41 ` Warren Young
2016-05-07 6:20 ` Thomas Wolff
2016-05-09 15:16 ` Warren Young [this message]
2016-05-09 18:30 ` Warren Young
2016-05-09 18:58 ` Warren Young
2016-05-09 20:57 ` Eric Blake
2016-05-09 21:29 ` Warren Young
2016-10-30 14:58 DAGwyn
2016-10-30 18:23 ` Ken Brown
2016-12-06 23:10 ` Eric Blake
2016-10-30 21:09 Steven Penny
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=741009F0-E57D-44DA-B728-68BDB4486DDD@etr-usa.com \
--to=wyml@etr-usa.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).