Date: Sun, 17 Jun 2007 16:44:17 +1000 From: Edwin Groothuis <edwin@mavetju.org> To: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> Cc: ports@FreeBSD.org Subject: Re: How to get a list of all kernel modules Message-ID: <20070617064417.GA1325@k7.mavetju> In-Reply-To: <4674D5B2.4000104@gmx.de> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070617064417.GA1325>