From: Bruno Haible <bruno@clisp.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Simon Josefsson <simon@josefsson.org>,
bug-gnulib@gnu.org, bug-standards@gnu.org
Subject: Re: egrep, fgrep, and install-info
Date: Sun, 27 Dec 2020 01:43:57 +0100 [thread overview]
Message-ID: <3937058.cZqfhRazpa@omega> (raw)
In-Reply-To: <d0d7eb3c-3990-8ed5-dfa0-031cf1e8f04d@cs.ucla.edu>
Paul Eggert wrote:
> ***************
> *** 174,179 ****
> --- 174,182 ----
> for parallel execution. For a list of known incompatibilities, see
> @ref{Portable Shell, Portable Shell Programming,, autoconf, Autoconf}.
>
> + Programs like @code{egrep} and @code{install-info} can be used in
> + rules that have a fallback if the programs are absent.
> + @xref{Standard Targets} for an example of this.
>
> It is a good idea to avoid creating symbolic links in makefiles, since a
> few file systems don't support them.
When you remove 'egrep', 'fgrep', or 'install-info' from the previously
allowed list of commands, everyone will ask: "ok, so now what replacement
should I use?"
1) For egrep and fgrep, probably the answer would be "use 'grep -E' or
'grep -F', respectively" — because POSIX supports these options.
<https://pubs.opengroup.org/onlinepubs/9699919799/utilities/grep.html>
Unfortunately, Solaris 10 doesn't:
$ type grep
grep is /usr/bin/grep
$ grep -F haible /etc/passwd
grep: illegal option -- F
Usage: grep -hblcnsviw pattern file . . .
$ grep -E '(haible|eggert)' /etc/passwd
grep: illegal option -- E
Usage: grep -hblcnsviw pattern file . . .
Likewise for /usr/5bin/grep.
2) For 'install-info', what would be the replacement? Even though Automake
knows how to handle its absence [1], it would be good to know.
Bruno
[1] https://www.gnu.org/software/automake/manual/html_node/Texinfo.html
next prev parent reply other threads:[~2020-12-27 0:44 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 ` 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 ` Bruno Haible [this message]
2020-12-27 1:12 ` egrep, fgrep, and install-info 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=3937058.cZqfhRazpa@omega \
--to=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=bug-standards@gnu.org \
--cc=eggert@cs.ucla.edu \
--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).