public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: cmp missing from base
Date: Sun, 30 Oct 2016 18:23:00 -0000	[thread overview]
Message-ID: <f1bf90c8-a956-d30e-b12a-8cbff57d4941@cornell.edu> (raw)
In-Reply-To: <ab6e82.247d6f40.454703d0@aol.com>

On 10/30/2016 4:05 AM, DAGwyn@aol.com wrote:
> I was unpleasantly surprised to find that the  "cmp" utility had been
> removed from the Cygwin base, and a search for "cmp" in  the Setup installer
> didn't find it.  (It used to exist.)  I eventually  found it hidden in the
> "diffutils" package.
> Upon searching the mailing list I  found some discussion, most of it being
> clueless.  "cmp" is widely used in  Unix makefiles!  It's a basic utility
> that has been around for over 40  years.  Utilities like that are so essential
> that it disrupts users when  they are removed.  There is a reason that
> POSIX specifies them!

I think the diffutils maintainer intended to add it to Base 
(https://sourceware.org/ml/cygwin/2016-05/msg00099.html), but maybe he 
forgot.  Eric?

Ken

--
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:[~2016-10-30 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-30 14:58 DAGwyn
2016-10-30 18:23 ` Ken Brown [this message]
2016-12-06 23:10   ` Eric Blake
  -- strict thread matches above, loose matches on Subject: below --
2016-10-30 21:09 Steven Penny
     [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
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

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=f1bf90c8-a956-d30e-b12a-8cbff57d4941@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).