From owner-svn-ports-head@FreeBSD.ORG Wed Jun 10 19:39:48 2015 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E793231F; Wed, 10 Jun 2015 19:39:48 +0000 (UTC) (envelope-from freebsd.contact@marino.st) 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 BF2F619AB; Wed, 10 Jun 2015 19:39:48 +0000 (UTC) (envelope-from freebsd.contact@marino.st) Received: from [10.10.0.87] (a83-160-76-75.adsl.xs4all.nl [83.160.76.75]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 25FBD43C32; Wed, 10 Jun 2015 14:39:41 -0500 (CDT) Message-ID: <5578927C.9070909@marino.st> Date: Wed, 10 Jun 2015 21:39:40 +0200 From: John Marino Reply-To: marino@freebsd.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Mathieu Arnold , marino@freebsd.org, Matthias Andree , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r389117 - head/databases/db48 References: <201506101808.t5AI8akA072276@svn.freebsd.org> <55788222.2090909@marino.st> <6E26F13BC369E591AB7ED533@atuin.in.mat.cc> In-Reply-To: <6E26F13BC369E591AB7ED533@atuin.in.mat.cc> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 19:39:49 -0000 On 6/10/2015 15:09, Mathieu Arnold wrote: > +--On 10 juin 2015 20:29:54 +0200 John Marino > | As a ramification, can you set DEPRECATED and EXPIRATION_DATE=2015-07-31 > | for all the bitcoin-related ports that refuse to transition off of db48? > | This port expiration has been extended several times, so why would > | these bitcoin ports feel the need to change? The maintainers know it > | will just get extended again. > > Bitcoin is engaged into converting from db48, yes, it'll take them years > (as in, many, I was about to write "a decade") to be confortable enough to > remove db48 support, so, can we drop this discussion now, or are we going > to revisit it every couple of months for the upcoming years ? > Yes, if db48 remove is extended every 2 months then I think it will probably get revisited every time it happens. There's really two logical choices: 1) remove the deprecation of db48 and commit to keeping it indefinitely 2) remove the bitcoin ports in two months. something like this taking "years" is pretty scary. It shouldn't be that hard. I'll defer to your knowledge and accept that it is. John