From owner-freebsd-ports@FreeBSD.ORG Sat Dec 6 14:12:28 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 98DCD16A4CE for ; Sat, 6 Dec 2003 14:12:28 -0800 (PST) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 681B743FCB for ; Sat, 6 Dec 2003 14:12:27 -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 38BEC14687; Sat, 6 Dec 2003 16:12:23 -0600 (CST) Message-ID: <3FD25400.70403@lonesome.com> Date: Sat, 06 Dec 2003 16:11:12 -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: Charles Swiger References: <20031205025342.04faf48b.sheepkiller@cultdeadsheep.org> <3FD013E7.7080302@lonesome.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: ports@FreeBSD.org 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: Sat, 06 Dec 2003 22:12:28 -0000 > GNATS would be more useful if it did this-- mailing the maintainer of > a port-- automatically if that person was not CC'ed on the PR > submission email. > > [ In other words, is it convenient to automate this "ability"? :-) ] IIRC someone was saying that the next version of GNATS (already available) has this ability? If not, my code could be made to do it with a little work (I do not currently scan the email headers, and GNATS has no interface to let you query them). And I've lost track of what the status of upgrading GNATS is as well. Of course if I ask one or two more times I may get stuck with the task ... > "Second opinion -- duplicates ports/misc/foo1 ... 4" > > ...or some such, indicating that the reviewer wants a second opinion > from someone else as to whether the port should be committed (and what > the issue is), leaving the PR open and the port uncommitted? Of course. That's why we have humans as committers :-) > I'm not convinced that putting a comprehensive list of reasons why a > committer should reject a new port in the Porter's Handbook is the > best way of encouraging people to contribute to the ports system. On > the other hand, I don't see any harm in the PH containing a suggestion > that being willing to maintain a port one submits is appreciated, will > contribute to rapid committal, etc. Well, I can live with this. OTOH claiming it will lead to more rapid commital might not actually be supported by the facts :-) but the part about it being appreciated should certainly go in. > Would it be useful to feed new port submissions to build machine for > testing to see whether they are broken before the port submission is > reviewed by a human? Hmph, misformatted PR's would still require > human intervention, so this probably wouldn't be that useful. I think it would be an interesting experiment to see if e.g. my code could be adapted to do that, but it would require some generalization of the bento scripts to be really useful. I have a number of such generalizations in the queue already :-) and bigger dragons to slay first, but think it would be a Neat Hack. mcl