From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: cmp missing from base
Date: Sat, 07 May 2016 06:20:00 -0000 [thread overview]
Message-ID: <572D891C.2040002@towo.net> (raw)
In-Reply-To: <29250DCF-60A0-4113-9834-25EA744E8F41@etr-usa.com>
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â? That is, if itâs on this page, it should be in Base:
>
> http://pubs.opengroup.org/onlinepubs/9699919799/idx/utilities.html
>
> That would exclude other things weâve always excluded, such as Perl.
>
> Iâm not suggesting that we make this rule a strict one. Most importantly, it cannot be an exclusion rule: Cygwin must contain things not in POSIX. Iâm just suggesting that it would be nice if Cygwin were as close to POSIX as practical out-of-the-box.
>
> By that latter, I mean without extra effort other than adjusting some setup.hint files. I mean, if there is a command on that list that doesnât even have a Cygwin package, I donât mean to propose with this rule that someone must go out and package it just to satisfy POSIX.
>
> As a counterexample, that list contains pax(1), which is currently in Archive, not Base, so by that rule, pax(1) should also move to Base.
>
> By that very example, though, I can argue against this proposed rule: as I understand it, pax(1) was added to POSIX at the same time they dropped cpio(1) and tar(1), thinking that by doing so, theyâd change existing practice, moving everyone over to pax(1). That just created a Standard in the XKCD sense:
>
> https://xkcd.com/927/
Thanks, Warren, for some metaphysical insights :)
Right, there isn't and shouldn't be a strict rule. But maybe there can
be a guideline, and more a guideline of common practice than of a 15th
standard. By decade-long practice as a Unix user, I was simply expecting
cmp to be basic, like I would expect tar. Maybe others would agree with
that, or maybe not...
Cheers
Thomas
--
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-07 6:20 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 [this message]
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
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=572D891C.2040002@towo.net \
--to=towo@towo.net \
--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).