From owner-freebsd-stable@FreeBSD.ORG Thu Jun 27 12:08:03 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2B375978 for ; Thu, 27 Jun 2013 12:08:03 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id E44C51F11 for ; Thu, 27 Jun 2013 12:08:02 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r5RC7nRA000314; Thu, 27 Jun 2013 06:07:49 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r5RC7n6E000311; Thu, 27 Jun 2013 06:07:49 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 27 Jun 2013 06:07:49 -0600 (MDT) From: Warren Block To: Garrett Wollman Subject: Re: portupgrade(1) | portmaster(8) -- which is more effective for large upgrade? In-Reply-To: <201306270505.r5R55RJD040660@hergotha.csail.mit.edu> Message-ID: References: <201306270505.r5R55RJD040660@hergotha.csail.mit.edu> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Thu, 27 Jun 2013 06:07:49 -0600 (MDT) Cc: bsd-lists@1command.com, freebsd-stable@freebsd.org 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: Thu, 27 Jun 2013 12:08:03 -0000 On Thu, 27 Jun 2013, Garrett Wollman wrote: > Having just gone through this in two different environments, I can > very very strongly recommend doing the following. It's not the "easy > button" of the TV commercials, but it will make things much much > easier in the future. This is an interesting procedure and should be made into a web-accessible document! Setting up a build machine for a network is a fairly common desire, and your procedure looks to be doing everything the newest way. > Then look through the output of "pkg query" to identify the leaf > packages that are the ones you actually wanted explicitly to have > installed. On a single machine, this can be approximated with portmaster's "--list-origins" option. It gives a list of root and leaf ports which can be edited to just the desired ones. Feed that list to portmaster on a system with no ports installed, and it will install the leaf ports and dependencies.