From owner-freebsd-ports@FreeBSD.ORG Mon Nov 10 20:29:42 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 205EB16A4CE for ; Mon, 10 Nov 2003 20:29:42 -0800 (PST) Received: from web13403.mail.yahoo.com (web13403.mail.yahoo.com [216.136.175.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 6B15543F93 for ; Mon, 10 Nov 2003 20:29:41 -0800 (PST) (envelope-from giffunip@yahoo.com) Message-ID: <20031111042941.73931.qmail@web13403.mail.yahoo.com> Received: from [63.171.232.247] by web13403.mail.yahoo.com via HTTP; Mon, 10 Nov 2003 20:29:41 PST Date: Mon, 10 Nov 2003 20:29:41 -0800 (PST) From: "Pedro F. Giffuni" To: freebsd-ports@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Ability for maintainers to update own ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: giffunip@asme.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Nov 2003 04:29:42 -0000 My $0.02 on this; - Having two port trees instead of one only means the changes will take longer to commit... to both trees :(. I personally think the Debian system is inferior to the ports tree even in management issues, but there is a Debian FreeBSD effort if someone really likes it that much ;-). - I actually like the idea of having someone check my ports before committing them. Even if, like me, you submit a lot of PRs, but will not take the responsibility to maintain them .. rest assured you won't be offered the commit bit. The key is being effective maintaining ports, and then.. maintainers screw up too. cheers, Pedro. __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree