From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 23 04:40:11 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 501E037B401 for ; Mon, 23 Jun 2003 04:40:11 -0700 (PDT) Received: from HAL9000.homeunix.com (ip114.bella-vista.sfo.interquest.net [66.199.86.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0A1243FB1 for ; Mon, 23 Jun 2003 04:40:10 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.9/8.12.9) with ESMTP id h5NBe5Ja031518; Mon, 23 Jun 2003 04:40:05 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.9/8.12.9/Submit) id h5NBe5sN031517; Mon, 23 Jun 2003 04:40:05 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Mon, 23 Jun 2003 04:40:05 -0700 From: David Schultz To: Sean Farley Message-ID: <20030623114005.GB12521@HAL9000.homeunix.com> Mail-Followup-To: Sean Farley , freebsd-hackers@freebsd.org References: <20030621103502.K18572@thor.farley.org> <20030622005852.GB59673@HAL9000.homeunix.com> <20030622092848.R28123@thor.farley.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030622092848.R28123@thor.farley.org> cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Replacing GNU grep revisited X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2003 11:40:11 -0000 On Sun, Jun 22, 2003, Sean Farley wrote: > On Sat, 21 Jun 2003, David Schultz wrote: > > > dds@ has expressed some interest in compiling the FSMs for regexps > > into native code, which would make it blazingly fast. See cvs-all@. > > As a practical matter, there are only a couple of zealots who care > > what kind of license grep is under, so replacing GNU grep with > > something that's ``almost as good as GNU grep'' is a regression IMO. > > If we were talking about a kernel module or library, of course, that > > would be a different matter. > > Let me clarify. As far as I have been able to find out, the big > hold-out on not considering FreeGrep was that it was too slow. I got > the time to be comparable. > > Reasons to consider for switching: > 1. GNU's grep -r option "is broken" according to the following post. > The only thing I have noticed is that FreeGrep has more options for > controlling how symbolic links are traversed. > http://groups.google.com/groups?hl=en&lr=lang_en&ie=UTF-8&selm=xzp7kchblor.fsf_flood.ping.uio.no%40ns.sol.net Sure, that sounds like a valid reason to switch. As others have pointed out, though, freegrep is not without problems. > 2. GNU's grep is using libgnuregex. The speed-up by dds@ would not be > felt? I was referring to freegrep, which I thought used the native libregex. In any case, if freegrep solves problems that GNU grep has, has the features people care about, is competitive in terms of performance, and has no known major bugs, then I would have no objections to it. As long as there are good technical reasons to switch, licensing advantages and performance are the least critical issues in my mind. We're not talking about a factor of 2, right?