BUG: Executables for "grep" package installed inconsistently

[Martin Buchholz]

I work on software that wants to be buildable by Cygwin.  It looks for
a /bin/egrep.exe, but can't find it.  Of course the system
administrator can easily add a symlink

/usr/bin/egrep.exe -> grep.exe
(It is possible that this won't work because egrep is one of those
evil programs that looks at $0...  I haven't investigated that
possibility.)

$ bunzip2 < grep-2.5-1.tar.bz2 | tar tvf - | grep usr/bin
drwxrwxrwx cgf/group         0 2002-03-20 21:16:15 usr/bin/
lrwxrwxrwx cgf/group         0 2002-03-20 21:16:15 usr/bin/egrep -> grep
lrwxrwxrwx cgf/group         0 2002-03-20 21:16:15 usr/bin/fgrep -> grep
-rwxrwxrwx cgf/group     85504 2002-03-20 21:16:15 usr/bin/grep.exe

If grep is installed as "grep.exe", then egrep should be installed as
"egrep.exe".  Ditto for fgrep.

Martin

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/