Date: Tue, 13 Sep 2011 16:05:32 -0500 From: Stephen Montgomery-Smith <stephen@missouri.edu> To: Oliver Fromme <olli@lurza.secnetix.de> Cc: "freebsd-ports@FreeBSD.ORG" <freebsd-ports@freebsd.org> Subject: Re: Thank you (for making the ports less boring). Message-ID: <4E6FC59C.5090509@missouri.edu> In-Reply-To: <201109131411.p8DEBTGA081124@lurza.secnetix.de> References: <201109131411.p8DEBTGA081124@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 09/13/2011 09:11 AM, Oliver Fromme wrote: > Stephen Montgomery-Smith wrote: > > particularly nasty thing to do. I get the impression that each > > committer has his own special way of doing this. For example, I have > > personally found that a simple grep won't work, because "grep xxx > > /usr/ports/*/Makefile*" just creates a line too long for the shell to > > handle. I use a shell construction involving "find" but I wonder how > > others do the same thing. > > cd /usr/ports > echo */*/Makefile* | xargs grep xxx That's amazing. It would never have occurred to me that "echo */*/Makefile*" works when "grep xxx */*/Makefile*". Is that because "echo" is a builtin command in csh (which is what I use)? I notice "/bin/echo */*/Makefile*" doesn't work. Is this documented somewhere?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E6FC59C.5090509>