From owner-freebsd-ports@FreeBSD.ORG Sun Jun 17 06:44:20 2007 Return-Path: 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 4918916A469 for ; Sun, 17 Jun 2007 06:44:20 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: from mail4out.barnet.com.au (mail4.barnet.com.au [202.83.178.125]) by mx1.freebsd.org (Postfix) with ESMTP id E78DE13C4C3 for ; Sun, 17 Jun 2007 06:44:19 +0000 (UTC) (envelope-from edwin@mavetju.org) Received: by mail4out.barnet.com.au (Postfix, from userid 1001) id 8524C37DD7D; Sun, 17 Jun 2007 16:44:18 +1000 (EST) X-Viruscan-Id: <4674D8420000E359D14C6B@BarNet> Received: from mail4auth.barnet.com.au (mail4.barnet.com.au [202.83.178.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail4.barnet.com.au (Postfix) with ESMTP id 582604248F6; Sun, 17 Jun 2007 16:44:18 +1000 (EST) Received: from k7.mavetju (k7.mavetju.org [10.251.1.18]) by mail4auth.barnet.com.au (Postfix) with ESMTP id 165CC37DD7B; Sun, 17 Jun 2007 16:44:18 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id B1991F4; Sun, 17 Jun 2007 16:44:17 +1000 (EST) Date: Sun, 17 Jun 2007 16:44:17 +1000 From: Edwin Groothuis To: "[LoN]Kamikaze" Message-ID: <20070617064417.GA1325@k7.mavetju> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4674D5B2.4000104@gmx.de> User-Agent: Mutt/1.4.2.3i Cc: ports@FreeBSD.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jun 2007 06:44:20 -0000 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. 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. What can it be used for? Questions like this for example. Or better CONFLICTS determination. Or historical information ("I get this file /usr/local/share/foo, but I can't find out who installed it") Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://www.mavetju.org/weblog/