From owner-freebsd-ports@FreeBSD.ORG  Sun Jun 17 07:46:43 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: ports@FreeBSD.org
Delivered-To: freebsd-ports@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id D579716A46C
	for <ports@FreeBSD.org>; Sun, 17 Jun 2007 07:46:43 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from elvis.mu.org (elvis.mu.org [192.203.228.196])
	by mx1.freebsd.org (Postfix) with ESMTP id C13A013C4B0
	for <ports@FreeBSD.org>; Sun, 17 Jun 2007 07:46:43 +0000 (UTC)
	(envelope-from kris@obsecurity.org)
Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196])
	by elvis.mu.org (Postfix) with ESMTP id 2A96D1A3C1A;
	Sun, 17 Jun 2007 00:46:04 -0700 (PDT)
Received: from rot13.obsecurity.org (rot13.obsecurity.org [192.168.1.5])
	by obsecurity.dyndns.org (Postfix) with ESMTP id 179175125A;
	Sun, 17 Jun 2007 03:46:43 -0400 (EDT)
Received: by rot13.obsecurity.org (Postfix, from userid 1001)
	id BBA59C283; Sun, 17 Jun 2007 03:46:42 -0400 (EDT)
Date: Sun, 17 Jun 2007 03:46:42 -0400
From: Kris Kennaway <kris@obsecurity.org>
To: Edwin Groothuis <edwin@mavetju.org>
Message-ID: <20070617074642.GB39370@rot13.obsecurity.org>
References: <20070616.213319.-1889956458.imp@bsdimp.com>
	<4674C9F6.60508@gmx.de> <4674CE41.7000103@gmx.de>
	<20070617.001516.-1615142562.imp@bsdimp.com>
	<4674D5B2.4000104@gmx.de> <20070617064417.GA1325@k7.mavetju>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20070617064417.GA1325@k7.mavetju>
User-Agent: Mutt/1.4.2.3i
Cc: ports@FreeBSD.org, "\[LoN\]Kamikaze" <LoN_Kamikaze@gmx.de>
Subject: Re: How to get a list of all kernel modules
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: Sun, 17 Jun 2007 07:46:43 -0000

On Sun, Jun 17, 2007 at 04:44:17PM +1000, Edwin Groothuis wrote:
> On Sun, Jun 17, 2007 at 08:33:22AM +0200, [LoN]Kamikaze wrote:
> > I see I misunderstood, sorry about that. So how about that one:
> > 
> > # find /usr/ports/ -type f -name pkg-plist -exec grep -El
> > '^@cwd[[:space:]]+/boot' \{} \; | sed -E 's|^/usr/ports/||1' | sed -E
> > 's|/pkg-plist$||1'
> > 
> > It only works with ports that have a pkg-plist file, though.
> 
> And which do @cwd in it. Doesn't work with multimedia/pvr250 for
> example.
> 
> This reminds me of a pet-project of me which I would like to restart,
> but which needs to cooperation from the maintainers of the package
> building clusters: A database of installed files. And a historical
> list of package build failures, but that one isn't relevant here.

Historical list of build failures going back to 2003 is available on
pointyhat.  I used to have logs going back to last century but had to
delete them for lack of space.

> What does it require? Not much: after each package built, somehow
> a notice gets send to a database backend which grabs the tarball,
> grabs the +CONTENTS files and stores that data.

Fill in the "somehows" and we can hook it up.

Kris