Date: Tue, 19 Feb 2013 13:00:25 -0600 From: Mark Felder <feld@feld.me> To: "A.J. 'Fonz' van Werven" <fonz@skysmurf.nl>, Chris Rees <utisoft@gmail.com> Cc: Bernard Higonnet <bthcom@higonnet.net>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: Is there an easy way to find out which port loads which library? Message-ID: <op.wsrk6ygo34t2sn@tech304.office.supranet.net> In-Reply-To: <CADLo83-nsAuUnrHVvkfDC_TC-Q9JL=ggn6%2BpdAYKFe16%2B55B%2Bg@mail.gmail.com> References: <51210EAD.3010009@higonnet.net> <20130217172125.GA63086@spectrum.skysmurf.nl> <CADLo83-nsAuUnrHVvkfDC_TC-Q9JL=ggn6%2BpdAYKFe16%2B55B%2Bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 17 Feb 2013 15:56:26 -0600, Chris Rees <utisoft@gmail.com> wrote:
> Most shells won't allow an argument list that long.
> % find /usr/ports -depth 3 -name pkg-plist -exec grep libfoobar.so \{} \;
> has been shown to be faster than hacking around arg list limits with
> echo |
> xargs.
The following may prove to be even faster as it fills the shell argument
list as full as possible for each execution of grep.
% find /usr/ports -depth 3 -name pkg-plist -exec grep libfoobar.so \{} +
(notice the + at the end)
It's something I picked up from here: http://www.etalabs.net/sh_tricks.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wsrk6ygo34t2sn>