From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: cmp missing from base
Date: Tue, 06 Dec 2016 23:10:00 -0000 [thread overview]
Message-ID: <451b2b97-5d46-0ad1-d5ff-47475db1b99c@redhat.com> (raw)
In-Reply-To: <f1bf90c8-a956-d30e-b12a-8cbff57d4941@cornell.edu>
[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]
On 10/30/2016 09:58 AM, Ken Brown wrote:
> 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?
Thanks for the reminder; I've finally found time to rectify it today.
Look for 3.5-2 to hit a mirror near you soon.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-12-06 23:10 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
2016-12-06 23:10 ` Eric Blake [this message]
-- 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=451b2b97-5d46-0ad1-d5ff-47475db1b99c@redhat.com \
--to=eblake@redhat.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).