From: Bruno Haible <bruno@clisp.org>
To: bug-gnulib@gnu.org, Simon Josefsson <simon@josefsson.org>
Subject: Re: cmp/diff
Date: Sat, 26 Dec 2020 18:32:47 +0100 [thread overview]
Message-ID: <2437960.L2bZbQ6S5l@omega> (raw)
In-Reply-To: <878s9k8rhw.fsf@latte.josefsson.org>
Hi Simon,
> Essentialy it boils down to:
>
> ../../gltests/test-binary-io.sh: line 8: cmp: command not found
> test-init.sh: failed test: err not empty: ../../gltests/init.sh: line 648: cmp: command not found
> ../../gltests/test-perror.sh: line 14: diff: command not found
'cmp' and 'diff' are among the programs that a 'configure' script and a Makefile
can assume to be present, see the GNU Coding Standards
<https://www.gnu.org/prep/standards/html_node/Utilities-in-Makefiles.html>.
> What do you think about rewriting these self-tests to avoid cmp/diff?
There is no adequate replacement. It would be possible to use 'md5sum'
instead of 'cmp'; but since 'md5sum' is not in the above list from the
GNU Coding Standards, this is not a useful direction.
Gnulib makes sure to pave over differences between different 'diff'
implementations; this was already a major headache. See tests/init.sh lines
589..669.
> https://gitlab.com/libidn/libidn/-/jobs/932649011
The Gitlab jobs typically start by installing packages into the build
environment. Yours has
$ pacman -Sy --noconfirm make gcc
I guess that adding 'diffutils' to this package list will solve the problem.
> I read the DEPENDENCIES file a bit more careful after noticing that it
> has several mandatory dependencies that I find questionable, and I
> noticed this in the beginning:
>
> The following packages are needed by maintainers for using
> 'gnulib-tool'.
>
> It doesn't say the packages are required for users building gnulib-based
> packages. I can live with having diffutils installed as a maintainer.
> Was this subtle distinction intentional?
Yes, of course, we make a distinction between the packages needed for
creating the tarballs and the packages needed to build+install the tarballs.
The GNU Coding Standards matters for the latter.
Bruno
next prev parent reply other threads:[~2020-12-26 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 16:24 cmp/diff Simon Josefsson via Gnulib discussion list
2020-12-26 17:32 ` Bruno Haible [this message]
2020-12-26 18:34 ` cmp/diff Simon Josefsson via Gnulib discussion list
2020-12-26 18:49 ` cmp/diff Bruno Haible
2020-12-26 19:12 ` cmp/diff Paul Eggert
2020-12-26 21:55 ` cmp/diff Simon Josefsson via Gnulib discussion list
2020-12-26 23:12 ` cmp/diff Paul Eggert
2020-12-27 0:07 ` cmp/diff Alfred M. Szmidt
2020-12-27 0:23 ` cmp/diff Paul Eggert
2020-12-27 1:05 ` cmp/diff Alfred M. Szmidt
2020-12-27 0:07 ` cmp/diff Alfred M. Szmidt
2020-12-27 0:43 ` egrep, fgrep, and install-info Bruno Haible
2020-12-27 1:12 ` Alfred M. Szmidt
2020-12-26 19:31 ` cmp/diff Paul Smith
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2437960.L2bZbQ6S5l@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=simon@josefsson.org \
/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).