From owner-freebsd-ports@FreeBSD.ORG Fri Dec 12 06:25:38 2008 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 906391065673 for ; Fri, 12 Dec 2008 06:25:38 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 493CD8FC13 for ; Fri, 12 Dec 2008 06:25:38 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so604778yxb.13 for ; Thu, 11 Dec 2008 22:25:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=rmo2GR1XZt5WKm0BEnLoCKcjDJ++aqgUlEFpk6wQuLs=; b=hVoubEZbn4PHInyLr+ZGDT76ueO/gMQBM1JVp2nNwSYw8FsLCKQmNXEZbQRh+D/08I ABR9NzI0xok7mp79HmGUdR7fJ8+5Tz7f+UUm4QY5vgtM4GInA1dwnWvUM7v/3xqeXVsh 5JtxaXuDR48PjEdF55bAT/57I0FYPlj8gtaOM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=VVmmT37zdO7R3R0Itm6O1iUN2QKspZMTaSIJx3Tdn83M4gkNThAWRc2hOr9zBav8Ch 7SKXcn7GX+Y2/dp7M3BEzMfUNXVeQzLUtwaMpkpSxi11QEzZgojyTJ3nY2NNQLxNY2Uo RirnIkACDOsIPl9wGTdN0JqNxN/SzhkjY1FVI= Received: by 10.90.104.20 with SMTP id b20mr2036627agc.50.1229063137565; Thu, 11 Dec 2008 22:25:37 -0800 (PST) Received: by 10.90.31.6 with HTTP; Thu, 11 Dec 2008 22:25:37 -0800 (PST) Message-ID: <790a9fff0812112225p3bb549d6iab5c76bffb86bea1@mail.gmail.com> Date: Fri, 12 Dec 2008 00:25:37 -0600 From: "Scot Hetzel" To: "Peter Beckman" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-ports@freebsd.org Subject: Re: portupgrade and freebsd-update: A better way? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2008 06:25:38 -0000 On 12/11/08, Peter Beckman wrote: > So I took on binary upgrading one of my FreeBSD servers today from > 6.2-RELEASE to 7.0-RELEASE. Many useful sites outline exactly how to do > this right, and they are mostly useful. > > Except when it comes to ports. > > > http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html > > http://www.cyberciti.biz/faq/howto-freebsd-server-upgrades/ > > You get a few production servers with 200+ ports installed, and upgrading > could take several days and lots of headaches and a lot of babysitting. > > Is there some sort of automated way that someone smart has figured out how > to determine which ports are actually affected by the upgrade, so I only > have to upgrade a hopefully small subset of installed ports? Are ALL the > libraries upgraded during the OS upgrade modified in a way that breaks ALL > existing ports? My gut says no, but my brain says it's not trivial to > match the two together to limit the number of times you have to rebuild a > port. > > Is there a better way? Does portsnap or portmanager or portupgrade keep > track? What have I missed? > If you have the compat6x port installed, you will not need to upgrade any of the 200+ ports on those productions servers. If you upgrade one port, you'll then need to upgrade all of it dependencies, as well as the ports that depend on these dependencies. To minimize your down time, you should set up a port build server that will build these 200+ ports as packages. On the production systems, you would use portupgrade to install the pre-built packages Scot