Your message dated Thu, 31 Aug 2017 09:52:21 +0200 with message-id <[email protected]> and subject line Re: bug#27763: egrep.sh: grep missing path has caused the Debian Bug report #863002, regarding grep missing path to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 863002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863002 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: grep Version: 2.20-4.1 cat /bin/egrep #!/bin/sh exec grep -E "$@" should replace with exec /bin/grep -E "$@" to reproduce: root@debian-512mb-fra1-01:/opt/firewall# bash root@debian-512mb-fra1-01:/opt/firewall# PATH=/usr/local egrep "any" /etc/* bash: egrep: command not found
--- End Message ---
--- Begin Message ---Control: tags -1 wontfix On Wed, 19 Jul 2017 14:05:54 +0200 Santiago Ruano =?iso-8859-1?Q?Rinc=F3n?= <[email protected]> wrote: > El 19/07/17 a las 02:56, Paul Eggert escribió: > > Santiago Ruano Rincón wrote: > > > > > As suggested by this user, it would be better if egrep/fgrep script > > > calls grep using its absolute path. > > > > Debian bug 863002 doesn't explain why it would be better, as the original > > bug report is evidently a case of misunderstanding how PATH works. > > The bug submitter sent me I private mail about that. I let him explain > it publicly answering to this mail. > For me, "it would be better" just because it makes egrep/fgrep call the > grep installed by the package. > > > Although we used to do it the way you're suggesting, the current way is > > better for users who want to specify their own 'grep' command with their own > > option preferences, and to have these preferences also apply to 'egrep' and > > 'fgrep'. See: > > > > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=19998 > > That makes sense. … Closing the bug giving rationale by upstream.
--- End Message ---
