Andrey Chernov wrote: > On Sun, Jun 15, 2008 at 09:17:01PM +0200, K?vesd?n G?bor wrote: >> Yes, of course, I haven't forgotten about your suggestion. First, I'd >> like to process the trivial errors, which come up like this one and make >> some tests myself. Then I'll think about this idea and ask portmgr to do >> an exp-run with BSD grep. I think that would be very valuable. > Please note that BSD grep is not localized (and can't be per design) and > works only with standard C locale. It may not affect ports system > processing but shurely affects real texts handling. That is very troubling. In this day and age localization is a requirement. I cannot imagine being supportive of adding something to the base that does not have this capability. I also found another gratuitous difference in behavior tonight, again from portmaster (which uses grep a LOT, which is why I thought to try it out in the first place). I do this type of thing in lots of places: pkg=/var/db/pkg/p5-Net-DNS-0.63 if grep -ql '^_at_pkgdep ' $pkg/+CONTENTS 2>/dev/null; then <do something> fi With gnu grep I get no output, and if there is a match the if statement just runs as I'd expect. With bsd grep I'm getting the name of the file as output. That's 3 strikes and you're out as far as I'm concerned. I think this project needs to come a lot closer to feature compatibility with gnu grep (including the ability to be localized) before it's ready for a wider audience. Of course, that's just my opinion. Doug -- This .signature sanitized for your protectionReceived on Mon Jun 16 2008 - 02:37:23 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:32 UTC