Re: Requiring grep which supports multiple -e options

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Ralf Wildenhues on 4/5/2008 4:58 AM:
|> | Is that requirement really necessary?  Does a "usual" configure
|> | script really need it?
|>
|> Probably not - at least, on inspection, neither autoconf nor coreutils
|> used 'grep -e'.
|
| No, but we documented for our users that AC_PROG_GREP provides this
| feature (of searching for such a grep).
|
| That would be backwards incompatible, no?  Also, it seems kind of
| arbitrary to relax requirements here, while we make other macros
| stricter in requiring standards conformance (gnulib is even much more
| extreme in this case).

Which means we can't change AC_PROG_GREP, but we can add
AC_PROG_GREP_SIMPLE which guarantees only a grep that meets the simpler
set of requirements.  Then we can reformulate AC_EGREP_CPP (and thus
AC_CHECK_HEADER) in terms of AC_PROG_GREP_SIMPLE (since that is documented
to only search a single pattern), but users who still need multiple -e for
other reasons can use AC_PROG_GREP.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkf3cDoACgkQ84KuGfSFAYBv2wCguHKbzF9SVE15v+sXZjUeRtKf
YDsAn146kyCTJtbAhDkAFSvYJIuvAO0I
=NAyf
-----END PGP SIGNATURE-----