From owner-freebsd-stable@FreeBSD.ORG Wed Jun 26 20:00:21 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E06F5CEF for ; Wed, 26 Jun 2013 20:00:21 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by mx1.freebsd.org (Postfix) with ESMTP id 648D519B1 for ; Wed, 26 Jun 2013 20:00:21 +0000 (UTC) Received: from mailout-de.gmx.net ([10.1.76.17]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0M3gWF-1U0vnD0uG1-00rDPP for ; Wed, 26 Jun 2013 22:00:14 +0200 Received: (qmail invoked by alias); 26 Jun 2013 20:00:14 -0000 Received: from f049195080.adsl.alicedsl.de (EHLO mandree.no-ip.org) [78.49.195.80] by mail.gmx.net (mp017) with SMTP; 26 Jun 2013 22:00:14 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX1/tXpxeBY/tEszrEI8xmR1SYb8SUTrqlIGWN++GaE gMTUjR9ySk1ri8 Received: from [IPv6:::1] (localhost6.localdomain6 [IPv6:::1]) by apollo.emma.line.org (Postfix) with ESMTP id 192FB23CE18 for ; Wed, 26 Jun 2013 22:00:13 +0200 (CEST) Message-ID: <51CB484C.3060209@gmx.de> Date: Wed, 26 Jun 2013 22:00:12 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade? References: <5e20544e3580a75759c3858f31894dc9.authenticated@ultimatedns.net> In-Reply-To: <5e20544e3580a75759c3858f31894dc9.authenticated@ultimatedns.net> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jun 2013 20:00:21 -0000 Am 26.06.2013 18:42, schrieb Chris H: > Greetings, > I haven't upgraded my tree(s) for awhile. My last attempt to rebuild after an updating > src && ports, resulted in nearly installing the entire ports tree, which is why I've > waited so long. Try as I might, I've had great difficulty finding something that will > _only_ upgrade what I already have installed, _and_ respect the "options" used during the > original make && make install, or those options expressed in make.conf. > As portupgrade(1) && portmaster(8) appear to be the most used in this scenario, > I'm soliciting opinions on which of these works best, or if there is something else to > better manage this situation. Is there such a thing as a FreeBSD upgrade "easy button"? > > Thank you for all your consideration. Chris, this time around, you will again rebuild almost your entire ports tree because some basic ports, such as Perl. Also, you will rarely be able to only upgrade what you already have installed because sometimes ports grow new requisite other ports you do not already have. I haven't used portupgrade in a long time because there was a period where it had fallen to bit-rot, but both tools are being maintained now. portupgrade has the decided advantage of being able to continue building some ports if another port failed as long as the failed port is not itself a requisite port for one that is yet to be built; portmaster bails out at the first error. portmaster, on the other hand, has a "rebuild everything" approach in the manual page, and can be used to list only leaf ports -- but that approach will require you to deinstall all ports so that the machine becomes unusable while it builds. There are other approaches, like using portmaster just to list this ports tree, and then use Tinderbox or poudriere to build packages in a chroot, and then only deinstall and install if you have all packages built successfully - but I am not familiar with automating this, not familiar with poudriere, and it requires a bit of work to get your options transferred to these build systems. Such a "build all packages first before you start deinstalling" would reduce the downtime, though. Hope that helps a little. Best regards Matthias Andree