From owner-svn-ports-head@FreeBSD.ORG Thu Aug 21 17:04:00 2014 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3A081B77; Thu, 21 Aug 2014 17:04:00 +0000 (UTC) Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id A04AC23CEB4; Thu, 21 Aug 2014 19:03:58 +0200 (CEST) Message-ID: <53F6267E.9020909@FreeBSD.org> Date: Thu, 21 Aug 2014 19:03:58 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: Bryan Drewery , ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r365566 - head/Tools/scripts References: <201408211556.s7LFuE0p041046@svn.freebsd.org> <53F61E42.4050104@FreeBSD.org> In-Reply-To: <53F61E42.4050104@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.18-1 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: Thu, 21 Aug 2014 17:04:00 -0000 Am 21.08.2014 um 18:28 schrieb Bryan Drewery: > On 8/21/2014 10:56 AM, Matthias Andree wrote: >> Author: mandree >> Date: Thu Aug 21 15:56:14 2014 >> New Revision: 365566 >> URL: http://svnweb.freebsd.org/changeset/ports/365566 >> QAT: https://qat.redports.org/buildarchive/r365566/ >> >> Log: >> Add a BerkeleyDB upgrade helper script in preparation of 4...4.7 removal. > > Thanks for making things simpler. > > We now have a script to run another script that was made to make > using ports simpler. The point is to abstract away the chaotic (miniscule input difference, major difference in result) differences along the various dimensions of port upgrading tools and local database management tools. I don't think a textual description for UPDATING would have been much shorter and the whole migration will look scary enough to users with the around-ten-step upgrade... And people WILL have multiple db4* versions on their typical system unless they manipulated /etc/make.conf.