From owner-freebsd-ports@FreeBSD.ORG Sun Oct 15 05:53:34 2006 Return-Path: X-Original-To: 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 0159516A403 for ; Sun, 15 Oct 2006 05:53:34 +0000 (UTC) (envelope-from eol1@yahoo.com) Received: from web51905.mail.yahoo.com (web51905.mail.yahoo.com [206.190.48.68]) by mx1.FreeBSD.org (Postfix) with SMTP id 6EF1B43D58 for ; Sun, 15 Oct 2006 05:53:33 +0000 (GMT) (envelope-from eol1@yahoo.com) Received: (qmail 82541 invoked by uid 60001); 15 Oct 2006 05:53:32 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=f1N+dAL5b2+I2zmGfhjOYW+l4qUcNK1Vbg02HIv7/cPe3E6/dw73/A5p8WLlmPjt0ogkLuxqyyL0YLxHnCmCEqViHEq1EkFnjc7ZW4ralWgkaNU+4G7s7yRa77YRD0lbmOlABT8ZwnsKPJKFDUq8C3nZrqSP3Q95hjkxlm/MixE= ; Message-ID: <20061015055332.82539.qmail@web51905.mail.yahoo.com> Received: from [65.243.223.8] by web51905.mail.yahoo.com via HTTP; Sat, 14 Oct 2006 22:53:32 PDT Date: Sat, 14 Oct 2006 22:53:32 -0700 (PDT) From: Peter Thoenen To: ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Sun, 15 Oct 2006 11:45:31 +0000 Cc: Subject: Port Bloat X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: eol1@yahoo.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Oct 2006 05:53:34 -0000 A couple months ago somebody posted a heads up on this list from the FreeBSD Ports Team about ports bloat and the massive influx of new software along with all the unmaintained ports. Has the port team ever thought about: A) Making a delete port pr request. This way port maintainers INSTEAD of marking 'transfer ownership to ports@freebsd.org' and hoping somebody takes it over one day could actually just delete ports they no longer wish to maintain. There should be some sort of WARN marking mechanism though (valid for X months (maybe 6)) that notifies any new user (or current via a portupgrade and EPOCH bumb) that this port is no longer maintained and scheduled for deletion unless one of them takes over maitainership by DATE. B) In line with A, has anybody thought about just marking ALL ports@freebsd.org as scheduled for deletion on X date. Thousands of people are using these ports, you can't tell me if they were actually scheduled to be deleted from the tree at least one of the users wouldn't take over maintainership. -Peter Just some ideas (as I have ports I own that I no longer care about and would like to delete), -Peter