From owner-freebsd-ports@FreeBSD.ORG Sun Sep 11 23:22:38 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 864C1106564A; Sun, 11 Sep 2011 23:22:38 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 60AFD1511EF; Sun, 11 Sep 2011 23:22:38 +0000 (UTC) Message-ID: <4E6D42BC.3070400@FreeBSD.org> Date: Sun, 11 Sep 2011 16:22:36 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: Warren Block References: <4E6B1AF5.7090900@tomse.dk> <4E6B227B.5050708@FreeBSD.org> <4E6B77EE.6030509@gmx.de> <20110910171530.GC23457@guilt.hydra> <20110910190549.GA23971@guilt.hydra> <20110911124910.GK13219@portland.byshenk.net> In-Reply-To: X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Chris Rees , freebsd-ports@freebsd.org, Greg Byshenk Subject: Re: Removed ports - looking from the bench X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Sep 2011 23:22:38 -0000 On 09/11/2011 13:35, Warren Block wrote: > Let me suggest a reasonable[1] plan: No. :) No more talking is necessary. Doing is necessary (or not, doesn't really matter to me at this point). I think Chris is right, a reasonable first step is a Handbook section on "How to recover a port from the CVS Attic." Beyond that if users want to get together and implement Carsten's idea, or another similar service, go for it! But at this point there is no more utility in continuing to talk about this topic. Everyone has said what they have to say, often numerous times, and there has been way more heat than light shed on the topic for some time now (as evidenced by Conrad's recent post where he realized that the issue is not nearly as dire as he thought it was after taking a look at what is actually happening). Time to move on, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/