From owner-freebsd-current@FreeBSD.ORG Wed Jul 28 15:34:07 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52B31106566C for ; Wed, 28 Jul 2010 15:34:07 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id 0B6668FC16 for ; Wed, 28 Jul 2010 15:34:06 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 217B314DC365; Wed, 28 Jul 2010 17:34:06 +0200 (CEST) X-Virus-Scanned: amavisd-new at server.mypc.hu Received: from server.mypc.hu ([127.0.0.1]) by server.mypc.hu (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 38hWi2JuX4Oo; Wed, 28 Jul 2010 17:34:03 +0200 (CEST) Received: from [192.168.1.105] (catv-80-99-92-167.catv.broadband.hu [80.99.92.167]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id C3E8714DB7CE; Wed, 28 Jul 2010 17:34:03 +0200 (CEST) Message-ID: <4C504DEA.9070405@FreeBSD.org> Date: Wed, 28 Jul 2010 17:34:02 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-PT; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: bf1783@gmail.com References: <4C5040E8.3050304@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, "b. f." Subject: Re: BSD grep fixes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Jul 2010 15:34:07 -0000 Em 2010.07.28. 17:26, b. f. escreveu: > I don't think that the current behavior of bsdgrep is necessarily bad > -- in fact it seems to me to be simple and intuitive: nothing is > excluded or included implicitly, and (I think) the last match wins, > unlike in gnu grep. I mention it only because it is different, and > you may want to consider how closely you want it to mimic the behavior > of gnu grep for the sake of compatibility. If bsdgrep already passed > a ports exp-run, and build/installworld now work without any problems, > then it may be simpler to just retain the current behavior. Either > way, though, the effect of overlapping --(in|ex)clude(-dir) options > should be explicitly mentioned in the manpage. Thank you, by the way, > for your efforts to provide us with good BSD-licensed tools. I hope > that you can find the time and energy to continue with the iconv, > regex, and other text-processing tool improvements. > Ok, thanks, then I'll just document it. Actually, I also think this behaviour is more intuitive, that's why I implemented it in this way. As for iconv, it needs a portbuild run and in first phase ports will still use GNU libiconv but BSD iconv will make its way into base if it passes the exp-run. Gabor