Re: grep-2.5.1a egrep/fgrep PATH problem

[Paul Eggert]

Charles Levert <address@hidden> writes:

> I don't have the priviledges to grant write
> access to CVS; Stepan is the one who does.

OK.  Stepan, can you please do that?  (I'm asking only reluctantly; I
don't have a lot of time to contribute to grep.  But at least I should
be able to clean up the messes I made.  :-)

> egrep fgrep: Makefile
>       (echo '#! /bin/sh'; \

Shouldn't the shell name be configured?

>       echo 'p="'`echo grep|sed '$(transform)'`'"' ; \
>       echo 'case "$$0" in' ; \
>       echo '  */*)' ; \
>       echo '    d="$${0%/*}/"' ; \

The ${0%/*}/ construction won't work in older shells: I suspect
they'll exit immediately when they detect it.

More important, this style of solution still doesn't conform to the
GNU coding standards.  For example, if I install grep into
/usr/local/bin and then move /usr/local/bin/fgrep to /usr/bin, then
the new /usr/bin/fgrep won't work as desired: it will call
/usr/bin/grep rather than /usr/local/bin/grep.

It's OK if we have this kind of solution as an installation-time
option, but it shouldn't be the default.