Date: Tue, 19 Jun 2007 16:12:37 +1000 From: Edwin Groothuis <edwin@mavetju.org> To: Kris Kennaway <kris@obsecurity.org> Cc: ports@FreeBSD.org Subject: Re: How to get a list of all kernel modules Message-ID: <20070619061236.GA24449@k7.mavetju> In-Reply-To: <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> <20070617074642.GB39370@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 17, 2007 at 03:46:42AM -0400, Kris Kennaway wrote: > > 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. I've put my ideas on paper (virtual paper), and they can be found at http://wiki.freebsd.org/PackageBuilderHistoricalData It describes what we have today, and what I think we can do with historical data. It consists of two parts: package contents and build logs. At this moment it's just the things I think are important or interesting, and give no guarantee that it will be as exicting as I think it is. I'll start with the latest bullet on that page, and see if we can get something nice out of 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?20070619061236.GA24449>