This is the mail archive of the
mailing list for the Cygwin project.
Re: cmp missing from base
- From: Warren Young <wyml at etr-usa dot com>
- To: The Cygwin Mailing List <cygwin at cygwin dot com>
- Date: Fri, 6 May 2016 19:41:21 -0600
- Subject: Re: cmp missing from base
- Authentication-results: sourceware.org; auth=none
- References: <572C697E dot 1090408 at towo dot net>
On May 6, 2016, at 3:53 AM, Thomas Wolff <email@example.com> 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:
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:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple