Date: Sun, 17 Jun 2007 03:46:42 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Edwin Groothuis <edwin@mavetju.org> Cc: ports@FreeBSD.org, "\[LoN\]Kamikaze" <LoN_Kamikaze@gmx.de> Subject: Re: How to get a list of all kernel modules Message-ID: <20070617074642.GB39370@rot13.obsecurity.org> In-Reply-To: <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> <20070617064417.GA1325@k7.mavetju>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070617074642.GB39370>