From owner-freebsd-ports@FreeBSD.ORG  Tue Feb 19 19:06:31 2013
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 5AF1EF8D
 for <freebsd-ports@freebsd.org>; Tue, 19 Feb 2013 19:06:31 +0000 (UTC)
 (envelope-from utisoft@gmail.com)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com
 [IPv6:2607:f8b0:4001:c03::22e])
 by mx1.freebsd.org (Postfix) with ESMTP id 10A1FFB8
 for <freebsd-ports@freebsd.org>; Tue, 19 Feb 2013 19:06:31 +0000 (UTC)
Received: by mail-ie0-f174.google.com with SMTP id k10so8785685iea.19
 for <freebsd-ports@freebsd.org>; Tue, 19 Feb 2013 11:06:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=x-received:mime-version:in-reply-to:references:from:date:message-id
 :subject:to:cc:content-type;
 bh=cv0mb75ULCmMGsp+zjh7nFl8aJQMXuDJrFFcTJFWv60=;
 b=ZOPQ/PEJ+seUcWe+4dqHUe+VfLxbGwUPi+FZ7SeVEtp+qG+wjGbt5LTefsxelklnfJ
 gmCVumvb5W6eoQVFrryQL0N7dc6zByGFrsjF3aEwpUVTatmnphcVQi5IeTKoDpHk4mBg
 PgtDxNVcIzJK/qz/zKA7qrh+qloCUEMwWzJErT5QfW/bVnvHoUIstx4H70D47xkmJSP5
 HaTWm7PkSN4DL8hYHnKgw87Nsh4/6bDJzgEtcbnOpxoldeONjCly5hvNwk7L76YqcQ0r
 jfUYRB51WvZ0f16iMJ6IhRKBP9CTLHBxJ6vL2zlTJ4JAFVTnyRNc1xatI1oog0BupAEb
 wOYg==
X-Received: by 10.50.152.132 with SMTP id uy4mr8982462igb.62.1361300788704;
 Tue, 19 Feb 2013 11:06:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.63.12 with HTTP; Tue, 19 Feb 2013 11:05:57 -0800 (PST)
In-Reply-To: <op.wsrk6ygo34t2sn@tech304.office.supranet.net>
References: <51210EAD.3010009@higonnet.net>
 <20130217172125.GA63086@spectrum.skysmurf.nl>
 <CADLo83-nsAuUnrHVvkfDC_TC-Q9JL=ggn6+pdAYKFe16+55B+g@mail.gmail.com>
 <op.wsrk6ygo34t2sn@tech304.office.supranet.net>
From: Chris Rees <utisoft@gmail.com>
Date: Tue, 19 Feb 2013 19:05:57 +0000
Message-ID: <CADLo8380aCdX7JSjWCS79uQTideftB=S8SK1QHT79XDMpDAxrQ@mail.gmail.com>
Subject: Re: Is there an easy way to find out which port loads which library?
To: Mark Felder <feld@feld.me>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bernard Higonnet <bthcom@higonnet.net>,
 "A.J. 'Fonz' van Werven" <fonz@skysmurf.nl>,
 FreeBSD Mailing List <freebsd-ports@freebsd.org>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Feb 2013 19:06:31 -0000

On 19 February 2013 19:00, Mark Felder <feld@feld.me> wrote:
> 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
>

I deliberately chose \; because most tests show no difference, and for
some reason it fails on csh :/

http://www.bayofrum.net/~crees/scratch/find-plus

Chris