From: Paul Eggert <eggert@cs.ucla.edu>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: simon@josefsson.org, bug-gnulib@gnu.org, bug-standards@gnu.org
Subject: Re: cmp/diff
Date: Sat, 26 Dec 2020 16:23:56 -0800 [thread overview]
Message-ID: <f8543dba-0030-4a97-948a-fd435c185918@cs.ucla.edu> (raw)
In-Reply-To: <E1ktJbK-00014Y-N8@fencepost.gnu.org>
On 12/26/20 4:07 PM, Alfred M. Szmidt wrote:
> install-info does not have an replacement, like say egrep/fgrep --
> this is how we install a dir entry for a info manual. Removing
> install-info would be a regression.
In practice, GNU installation procedures use install-info in the way
that's described in the proposed patch: they test whether install-info
is available, and if so they use it. The make-stds.texi file already
recomments this practice in its "Standard Targets" section. The proposed
patch is doing merely making make-stds coherent; it's not advocating any
change to existing best practice for install-info.
next prev parent reply other threads:[~2020-12-27 0:24 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 ` cmp/diff Bruno Haible
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 ` Paul Eggert [this message]
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=f8543dba-0030-4a97-948a-fd435c185918@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=ams@gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=bug-standards@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).