From owner-freebsd-ports@FreeBSD.ORG Tue Apr 26 22:15:58 2011 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28444106564A for ; Tue, 26 Apr 2011 22:15:58 +0000 (UTC) (envelope-from jerry@seibercom.net) Received: from mail-gw0-f68.google.com (mail-gw0-f68.google.com [74.125.83.68]) by mx1.freebsd.org (Postfix) with ESMTP id CDEC48FC15 for ; Tue, 26 Apr 2011 22:15:57 +0000 (UTC) Received: by gwj19 with SMTP id 19so177450gwj.7 for ; Tue, 26 Apr 2011 15:15:57 -0700 (PDT) Received: by 10.236.189.69 with SMTP id b45mr1665474yhn.293.1303856157047; Tue, 26 Apr 2011 15:15:57 -0700 (PDT) Received: from scorpio.seibercom.net (twdp-174-109-142-001.nc.res.rr.com [174.109.142.1]) by mx.google.com with ESMTPS id h4sm81788yhm.80.2011.04.26.15.15.55 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Apr 2011 15:15:56 -0700 (PDT) Received: from seibercom.net (zeus [192.168.1.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: freebsd-ports.user@scorpio.seibercom.net) by scorpio.seibercom.net (Postfix) with ESMTPSA id 3QJzJp5Sjcz2CG54 for ; Tue, 26 Apr 2011 18:15:54 -0400 (EDT) Date: Tue, 26 Apr 2011 18:15:54 -0400 From: Jerry To: freebsd-ports@freebsd.org Message-ID: <20110426181554.6ddd9393@seibercom.net> In-Reply-To: <4DB73EFD.1070502@FreeBSD.org> References: <4DB6165F.1010806@FreeBSD.org> <20110426024122.GA38579@comcast.net> <20110426163424.GB38579@comcast.net> <20110426141209.0d07bccf@seibercom.net> <20110426184315.GA2320@libertas.local.camdensoftware.com> <19895.13977.553973.609431@jerusalem.litteratus.org> <4DB73EFD.1070502@FreeBSD.org> Organization: seibercom.net X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.1; amd64-portbld-freebsd8.2) Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEUeH4oAAI3//v8LDHmw s8gyNZ/b3ej7+vn+/v////+PjIc8Plaj/TnQAAACNElEQVQ4jaXUvW/aQBQAcFtKGZLFT+YY 3D1SR9SKoRMncE3IggU4kicGi1JYOgQwyYrgnLlSzhsoNkTuVJEp+ef6ztiAoV3aJ+QPfufn s987S/5fQvoXYPjztmfc514Ks+5JfGUCfrzt4+VabF+jwEV4DGEXN8N4p16sPLxHX07/V3qX yfF5D2H6K4V8j9NkyAphvkjBembD5PDFk3zeTzP1jcksyaV9w+d4ELmUoOp8N2p8uQVyhTAT uawnKNH2mie5lJp48mscUcbJUvg0mR6APwAoye9AMyWozY4gAh0vcxa5FJ4TKCuODESWtfkB 8AEQSupUXNIYH8FSC2w8X3eMBNbbVJpJ7MgECO5yJ9DUEWCYkzNAlsRsgwLQ1GkWqELbkDOh 1bUzoHagYkNh9MXlK/MQoA42gTxz2bhPM2DJedm8MZx6cNfJgEZJ5cmwPp5FZ/Ye8O2qTrFV dgOrHkZRBoheJiGrRquwAhnQ6GeTePPerWVmQelAQ5lwNqtvQd2lcooAV74/zR1BIRS19fy5 ru+B/8ReW9pYKMPjt609zDaitHHTGOO+Zu7gHvsKE7XbeE1QVuJXomIFuZgUJdXQdhpqEELc /e8RLjfi+cQ01yMdWot8UcCVxEWHEkcUrsDGuhaIEoM9kfgAR6jxHcmEV7tNURAl8KTHN9iF McKGFHGO62O62UMpbmlVuogQ7ndL8zXCiLeBy3xpfrqaXS/+AHDG4o8AvhuPeezD/3xL/hy/ Adjlg2odglF2AAAAAElFTkSuQmCC Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: saving a few ports from death X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-ports@freebsd.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Apr 2011 22:15:58 -0000 On Tue, 26 Apr 2011 14:54:05 -0700 Doug Barton articulated: > On 04/26/2011 14:18, Robert Huff wrote: > > It is also possible it is only important to a fairly small > > number ... but to those it is absolutely crucial. > > Fair enough, then one of them needs to step forward to maintain the > port. :) > > FWIW, I think that the person who suggested deleting the port as a > way to gain a metric of its popularity was joking ... Sorry, but I was dead serious. "Don't Know What You Got (Till It's Gone)" "Cinderella" If no one steps up claiming to need the port, then good riddance. If on the other hand a user claims a valid use of the port, let them take responsibility for it or find someone who will. Leaving intact ports that either don't build, cannot be fetched, etcetera does not really make a lot of sense. -- Jerry ✌ jerry+ports@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________