Date: Sun, 15 Jun 2008 21:17:01 +0200 From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <gabor@t-hosting.hu> To: Diomidis Spinellis <dds@aueb.gr> Cc: hackers@FreeBSD.org, Doug Barton <dougb@FreeBSD.org>, current@FreeBSD.org, "Sean C. Farley" <scf@FreeBSD.org>, Max Khon <fjoe@samodelkin.net> Subject: Re: CFT: BSD-licensed grep [Fwd: cvs commit: ports/textproc/bsdgrep Makefile distinfo] Message-ID: <48556AAD.9010602@t-hosting.hu> In-Reply-To: <4854C96A.1080603@aueb.gr> References: <485453F2.60507@FreeBSD.org> <4854BC29.3060507@FreeBSD.org> <4854C96A.1080603@aueb.gr>
next in thread | previous in thread | raw e-mail | index | archive | help
Diomidis Spinellis escribió: > Doug Barton wrote: >> I use the following construct in portmaster, where pdb=/var/db/pkg, >> origin is set to the origin of a given port, and ro_opd is usually >> empty, but can be another origin directory or the same one. To >> guarantee that you should get some kind of results you can test with >> origin=devel/gettext. >> >> egrep -l "DEPORIGIN:($origin|$ro_opd)$" $pdb/*/+CONTENTS >> >> Obviously this works in portmaster with the gnu grep, but if ro_opd >> is unset with the bsd grep I get: >> >> egrep: empty (sub)expression > > To avoid these problems I had proposed to instrument getopt to write > options passed through argv in a file, build all our ports, and look > at the options used. 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. Regards, -- Gabor Kovesdan EMAIL: gabor@FreeBSD.org WWW: http://www.kovesdan.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48556AAD.9010602>