Date: Wed, 28 Jul 2010 17:34:02 +0200 From: Gabor Kovesdan <gabor@FreeBSD.org> To: bf1783@gmail.com Cc: freebsd-current@FreeBSD.org, "b. f." <bf1783@googlemail.com> Subject: Re: BSD grep fixes Message-ID: <4C504DEA.9070405@FreeBSD.org> In-Reply-To: <AANLkTi=d0Ev_JwE5AFHNMSyPrWYTd7PYTSGn2W91prHA@mail.gmail.com> References: <AANLkTimJiV1s3KNsCKsqT_dNiqMyRuOFpK47AD4QyMUO@mail.gmail.com> <4C5040E8.3050304@FreeBSD.org> <AANLkTi=d0Ev_JwE5AFHNMSyPrWYTd7PYTSGn2W91prHA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C504DEA.9070405>