From owner-freebsd-ports@FreeBSD.ORG  Mon Nov 10 06:09:03 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 D35FB16A4CE
	for <freebsd-ports@freebsd.org>; Mon, 10 Nov 2003 06:09:03 -0800 (PST)
Received: from bloodwood.hunterlink.net.au (mail.hunterlink.net.au
	[203.12.144.18])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9108B43FDD
	for <freebsd-ports@freebsd.org>;
	Mon, 10 Nov 2003 06:09:02 -0800 (PST)
	(envelope-from boris@brooknet.com.au)
Received: from [202.7.67.16] (as1-p16.mait.hunterlink.net.au [202.7.67.16])
	hAAE8xaF006187
	for <freebsd-ports@freebsd.org>; Tue, 11 Nov 2003 01:09:00 +1100
From: Sam Lawrance <boris@brooknet.com.au>
To: freebsd-ports@freebsd.org
In-Reply-To: <3FAF7337.6050708@fillmore-labs.com>
References: <1068458390.38101.19.camel@dirk.no.domain>
	 <3FAF7337.6050708@fillmore-labs.com>
Content-Type: text/plain
Message-Id: <1068469810.38101.55.camel@dirk.no.domain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Tue, 11 Nov 2003 00:10:10 +1100
Content-Transfer-Encoding: 7bit
Subject: Re: Ability for maintainers to update own ports
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Nov 2003 14:09:03 -0000

On Mon, 2003-11-10 at 22:15, Oliver Eikemeier wrote: 
> You might want to have a look into NetBSD's pkgsrc-wip:
> It's not exactly what you propose, but a step in the same direction: get more
> people involved in the ports system.

pkgsrc-wip seems to be a great idea - rather than having new ports and
updates only tucked away in PRs, they're easily available for general
review and improvement. This is an excellent feature.

However, there's still that rift between pkgsrc-wip and the main pkgsrc
repository. While pkgsrc-wip provides a valuable testing ground, it adds
another (optional) layer to the process of creating and maintaining
ports. (I completely acknowledge that I say this without having any
experience of using pkgsrc-wip). I think it can be improved upon.

I think I sort of have an idea of what I have an idea of :) I'll try to
consolidate my thoughts and perhaps knock up a plan and prototype.

Regards
-Sam.