From owner-freebsd-ports@FreeBSD.ORG Mon Sep 5 23:06:09 2011 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1BA92106566C; Mon, 5 Sep 2011 23:06:09 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id D514F8FC0A; Mon, 5 Sep 2011 23:06:08 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p85N64eL025576 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 5 Sep 2011 16:06:04 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p85N64q3025572; Mon, 5 Sep 2011 16:06:04 -0700 (PDT) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA20721; Mon, 5 Sep 11 15:48:41 PDT Date: Mon, 05 Sep 2011 22:48:30 -0700 From: perryh@pluto.rain.com To: dougb@freebsd.org, utisoft@gmail.com, jhs@berklix.com Message-Id: <4e65b42e.M5K+to11vAdk/UTk%perryh@pluto.rain.com> References: <201109050933.p859XEbP004874@fire.js.berklix.net> <4E64C35A.50004@FreeBSD.org> In-Reply-To: <4E64C35A.50004@FreeBSD.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: sysutils/cfs 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: Mon, 05 Sep 2011 23:06:09 -0000 Doug Barton wrote: > On 09/05/2011 02:33, Julian H. Stacey wrote: > >>> It is not responsible to threaten to remove ports without > >>> warning between releases for non urgent reasons. > > We understand that this is your perspective, however the community > in general has a different idea. I suppose it may depend on how one defines "the community". AFAIK there are maybe half a dozen or so developers who have recently put themselves on record as supporting the current, agressive deprecation campaign. The number who have posted in opposition may well be smaller, so you are probably right if "the community" is defined as consisting only of those two groups :) > >>> Better to deprecate such non urgent ports, & wait a while > >>> after next release is rolled, to give release users a warning > >>> & some time to volunteer ... > > That's an interesting idea, but incredibly unlikely to happen. It _certainly_ won't happen if those in charge refuse to try it! > > The Attic is the standard myopic excuse, ignoring not all > > FreeBSD release users have CVS, > > It is available to everyone, and trivial to configure. The fact > that removed ports still exist in CVS is not a "myopic excuse," > it's a fact. Last I checked (8.1 release) there was no mention of the Attic in either the Handbook or the Porter's Handbook. Do I hear a volunteer to add a section describing the Attic and how to retrieve things from it? (I am not qualified to write such a section -- I'm not that familiar with CVS.) > We need to make the best decisions we can to provide the best > support possible for the largest percentage of our users. But how do we know what "the best support possible" consists of? I somehow doubt that anyone has polled even a modest percentage of our users -- to find out what they would consider "the best support possible" -- since AFAIK we have no way of even _identifying_ more than a tiny fraction of the user base. My *guess* is that "the largest percentage of our users" are what Julian calls "release users" -- those who install a release and corresponding ports, and don't touch it subsequently until they become aware of a problem. They _may_ follow the security branch for their base release, but that won't make them aware of issues that have turned up in ports. Instead, they will be unpleasantly surprised that a port they use has disappeared sometime after they installed it and before they have occasion to (attempt an) upgrade.