Date: Tue, 29 Nov 2011 00:58:27 +0100 From: =?UTF-8?B?R8OhYm9yIEvDtnZlc2TDoW4=?= <gabor@t-hosting.hu> To: d@delphij.net Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r228099 - head/usr.bin/grep Message-ID: <4ED42023.3080301@t-hosting.hu> In-Reply-To: <4ED3ED83.9000001@delphij.net> References: <201111282016.pASKGtcf007383@svn.freebsd.org> <4ED3ED83.9000001@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2011.11.28. 21:22, Xin LI wrote: > This is useful but could be confusing since xzgrep's behavior could be > different from zgrep. What do you refer to exactly? That zgrep is GNU grep and xzgrep is BSD grep? I acknowledge that this is not documented but xzgrep is a non-standard addition so personally think it is acceptable. Someone called my attention to the archivers/xz port that had a wrapper script for grep, callled xzgrep. This was installed with the port but is not installed in base any more so I got the suggestion to implement it in BSD grep and I think it is a better idea than a wrapper script and it was easy to support. So with this change, this functionality can be used again w/o installing the port although it is not documented. > > Another topic would be ObsoleteFiles.inc (or > OptionalObsoleteFiles.inc) needs to be updated for this as well. I don't think they should be updated. From now on, xzgrep and such are always created and they always point to BSD grep, which can be /usr/bin/grep or /usr/bin/bsdgrep depending on WITH_BSD_GREP. But they always exist and point to one or another. I cannot think of any case when they should be removed. Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ED42023.3080301>