From owner-freebsd-ports@FreeBSD.ORG  Wed Apr  9 18:10:35 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4DCD7424
 for <freebsd-ports@freebsd.org>; Wed,  9 Apr 2014 18:10:35 +0000 (UTC)
Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 212B21A95
 for <freebsd-ports@freebsd.org>; Wed,  9 Apr 2014 18:10:32 +0000 (UTC)
Received: from [192.168.0.20] (unknown [130.255.19.191])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by shepard.synsport.net (Postfix) with ESMTP id 4B54343BA8;
 Wed,  9 Apr 2014 13:10:15 -0500 (CDT)
Message-ID: <53458CF0.4080900@marino.st>
Date: Wed, 09 Apr 2014 20:09:52 +0200
From: John Marino <freebsd.contact@marino.st>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Christian Weisgerber <naddy@mips.inka.de>, freebsd-ports@freebsd.org
Subject: Re: FreeBSD ports which are currently scheduled for deletion
References: <mailman.0.1396958400.6606.freebsd-ports@freebsd.org>
 <5344005C.4030503@aldan.algebra.com>
 <20140408185537.69d5cd6e@kalimero.tijl.coosemans.org>
 <53442E10.6060907@aldan.algebra.com>
 <20140409002033.5a2d9850@kalimero.tijl.coosemans.org>
 <slrnlkb2do.83i.naddy@lorvorc.mips.inka.de>
In-Reply-To: <slrnlkb2do.83i.naddy@lorvorc.mips.inka.de>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: marino@freebsd.org
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Wed, 09 Apr 2014 18:10:35 -0000

On 4/9/2014 19:56, Christian Weisgerber wrote:
> On 2014-04-08, Tijl Coosemans <tijl@coosemans.org> wrote: 
>> Then, once it is reasonable to assume that a port is unused it is first
>> marked deprecated which gives users some time to step forward.
> 
> There seems to be the general problem, seen again and again, that
> users only learn of a port's deprecation status when it is finally
> removed and not in the preceding grace period.

I find this highly doubtful.
I will give you that binary package users won't know the package is
deprecated or their is even a problem until the package is no longer
available, but somebody is going to see if if they build from source.

OTOH, if somebody only rebuilds every 15 months, the deprecation period
could come and go.  I guess the ultimate solution is that "pkg info"
shows packages that are deprecated.

In the meantime -- it's still a non-problem as long as "svn revert" works.

John