From owner-freebsd-ports@FreeBSD.ORG  Wed Jun 10 20:52:37 2009
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id A2F06106567A;
	Wed, 10 Jun 2009 20:52:37 +0000 (UTC)
	(envelope-from wxs@atarininja.org)
Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158])
	by mx1.freebsd.org (Postfix) with ESMTP id E79CC8FC12;
	Wed, 10 Jun 2009 20:52:36 +0000 (UTC)
	(envelope-from wxs@atarininja.org)
Received: by syn.atarininja.org (Postfix, from userid 1001)
	id 4554D5C37; Wed, 10 Jun 2009 16:52:36 -0400 (EDT)
Date: Wed, 10 Jun 2009 16:52:36 -0400
From: Wesley Shields <wxs@FreeBSD.org>
To: Mel Flynn <mel.flynn+fbsd.ports@mailing.thruhere.net>
Message-ID: <20090610205236.GD65705@atarininja.org>
References: <20090610132647.GC40713@atarininja.org>
	<200906101244.43479.mel.flynn+fbsd.ports@mailing.thruhere.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200906101244.43479.mel.flynn+fbsd.ports@mailing.thruhere.net>
User-Agent: Mutt/1.5.19 (2009-01-05)
Cc: ports@freebsd.org, python@freebsd.org, freebsd-ports@freebsd.org,
	miwi@freebsd.org
Subject: Re: Python 2.6 update with portmaster
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/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: Wed, 10 Jun 2009 20:52:38 -0000

On Wed, Jun 10, 2009 at 12:44:42PM -0800, Mel Flynn wrote:
> On Wednesday 10 June 2009 05:26:47 Wesley Shields wrote:
> 
> > It will be quite slow compared to using pkg_which (the normal method) so
> > be patient.
> 
> Does pkg_which use the pkgdb? If so, maybe we could have pkg_info grow a cache 
> for future encounters, or we can create one:

My guess is that pkg_which is using pkgdb, which is why it is
significantly faster.

> % grep -v '^@' /var/db/pkg/*/+CONTENTS >/tmp/pkg_info.cache
> % FOUND=`sed -ne 's,^/var/db/pkg/\(.*\)/+CONTENTS:lib/python2.6/site-
> packages/xcbgen/error.py$,\1,p' /tmp/pkg_info.cache`; echo $FOUND
> xcb-proto-1.4
> 
> So:
> 's,^${PKG_DBDIR}/\(.*\)/+CONTENTS:$$f$$,\1,p'

I think there is a SoC project in the works to make our pkg utilities
much better. I don't know any of the details but I can only hope that
speed is one of the things being improved.

> > [1]: http://people.freebsd.org/~wxs/python26-portmaster.diff
> 
> What's this for?
> +JOBS=	sysctl -n kern.smp.cpus
> 
> Should be != if it's gonna be used, but it's not referenced anywhere else	 
> that I can see.

It's used in XARGS_CMD to provide a bit of parallelism in an effort to
be a bit faster. In my opinion the number can be increased much further
than kern.smp.cpus but I'm not in a position to figure out how far to
push it. The value used is better than nothing.

-- WXS