From owner-freebsd-ports@FreeBSD.ORG Thu Dec 4 20:58:27 2003 Return-Path: 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 5A95C16A4CE; Thu, 4 Dec 2003 20:58:27 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 505E043F75; Thu, 4 Dec 2003 20:58:25 -0800 (PST) (envelope-from linimon@lonesome.com) Received: from lonesome.com (cs242719-195.austin.rr.com [24.27.19.195]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.soaustin.net (Postfix) with ESMTP id 63FC21468E; Thu, 4 Dec 2003 22:58:24 -0600 (CST) Message-ID: <3FD0104E.7060900@lonesome.com> Date: Thu, 04 Dec 2003 22:57:50 -0600 From: Mark Linimon User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030713 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Price References: <20031205044324.GE55425@bsd.havk.org> In-Reply-To: <20031205044324.GE55425@bsd.havk.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: ports@freebsd.org cc: clayton rollins Subject: Re: [DRAFT] ports contributor's guide X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Dec 2003 04:58:27 -0000 IMHO there are two better solutions, that highlight the unmaintained ports that have build problems (and, in the second case, PRs as well). The first is any of the bento links such as http://bento.freebsd.org/errorlogs/i386-5-full/index-maintainer.html, where you can substitute -- for 'i386-5-full'. The second is to link to one of my reports with the following precooked link: http://lonesome.dyndns.org:4802/bento/errrorlogs/portsconcordanceformaintainer.py?maintainer=ports%40freebsd.org. Bit of a tongue-twister, and a little bit long to display since it's 2K lines, but it _does_ have all the information you want. I can generate that report as a static report if there is demand for it (i.e. you don't have to wait for the SQL to run), or indeed, if there is sufficient demand for it, a subset of it (by category perhaps? by 'only ones with errors'? I'm open to suggestions. It's all driven off the same database so new reports are not hard to generate). Again, my hope is to get this code running on one of the FreeBSD.org machines to make it more visible for things like this (and to free up the bandwidth here at the house :-) ) mcl