From owner-freebsd-ports Mon Jan 20 5:47:32 2003 Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FD1437B401 for ; Mon, 20 Jan 2003 05:47:30 -0800 (PST) Received: from mail.droso.net (koala.droso.net [193.162.142.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85B0943EB2 for ; Mon, 20 Jan 2003 05:47:29 -0800 (PST) (envelope-from erwin@mail.droso.net) Received: by mail.droso.net (Postfix, from userid 1001) id 72B413305E; Mon, 20 Jan 2003 14:47:27 +0100 (CET) Date: Mon, 20 Jan 2003 14:47:27 +0100 From: Erwin Lansing To: Edwin Groothuis Cc: ports@freebsd.org Subject: Re: Bento Reporting Enhancements Message-ID: <20030120134727.GG12043@droso.net> Mail-Followup-To: Edwin Groothuis , ports@freebsd.org References: <20030120132715.GA27491@k7.mavetju> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dkEUBIird37B8yKS" Content-Disposition: inline In-Reply-To: <20030120132715.GA27491@k7.mavetju> X-Operating-System: FreeBSD/i386 4.7-RELEASE-p3 User-Agent: Mutt/1.5.1i Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --dkEUBIird37B8yKS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 21, 2003 at 12:27:15AM +1100, Edwin Groothuis wrote: > Hi, Hej,=20 >=20 > I was wondering if Port Building Reporting could be done better. > Right now, the building of ports is done on several different > host-systems, different OSses and at the end you have a log-file > which gets batch-processed into a couple of HTML files. There is > no way to quickly check the history of the build of a port (when > did it start to stop building correctly, different per platform and > OS version of course (what did you expect :-), you can't quickly > see if the port builds, or doesn't, on a different platform and > there is no way to get a small overview of all ports failing with > a perl-error, you get the information of all ports. Etc etc etc. >=20 > Yes, to do these things you need a database. Well, let us get a > database then. If after each build (or attemtp to build :-) the > logfile and some meta-information (which processor, which OS version) > is send to an account@machine which processes it and stores it in > the database. Then with a webbrowser, webserver and a couple of PHP > scripts you can access the data there. Rocket-science, isn't it? >=20 [snip pros-cons] I think this would be an excelent idea. I've actually wondered about these missing "features" a couple of times. If we can make this an official FreeBSD service, I'll be happy to lend a hand. I've always wanted to be a rocket scientist :o) -erwin --=20 _._ _,-'""`-._ Erwin Lansing (,-.`._,'( |\`-/| http://droso.org/ erwin@lansing.dk `-.-' \ )-`( , o o) http://fnidder.dk/ -bf- `- \`_`"'- --dkEUBIird37B8yKS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+K/3vqy9aWxUlaZARAqV6AJ0SN1YZd9cF7gssh5f/5TairODnjgCfS9bL dOXBhdjkXLlpmbRmoiVJCXc= =C5FJ -----END PGP SIGNATURE----- --dkEUBIird37B8yKS-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message