From owner-freebsd-ports@FreeBSD.ORG Fri Dec 12 05:46:39 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 E0C551065676 for ; Fri, 12 Dec 2008 05:46:39 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id B47DC8FC08 for ; Fri, 12 Dec 2008 05:46:39 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1219013rvf.43 for ; Thu, 11 Dec 2008 21:46:39 -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=QOgX4O7IvRdyMAFsy/Q8uUwWI1Y1/xfLL5avg+/R/JU=; b=Mo9voehzpY98CLf/V84KKpbouX2qxwlbMcD8WDhGYpnQMPXHPA9543ORvtO+bUg81+ raeVkqVquV0ro8VknU/T694AcqetJin7dLE1lVjHKq1ER/Dp3CI2jaRMyFZq3WIKJeL9 Y6R5QB3iGTHNnjLNTNgUVLlxP1dABIf2kwaz8= 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=U/QFm3kBrJZ7um+dbC1KxiozbQhtOMCaJY45c30WngBjS3bHprgEeS4H9ZzQNqT/sv Eq3entOesxobrHAoBoUg4/BhNCcTQKLhlm/NxvDVTueVhQ5+jeWctuQNnmtZRSt0ks0k 822FEBu3T1vmYc1yEOUyO2FBw5QZNY+Lp1fCY= Received: by 10.141.5.20 with SMTP id h20mr1699528rvi.299.1229060799347; Thu, 11 Dec 2008 21:46:39 -0800 (PST) Received: by 10.140.158.13 with HTTP; Thu, 11 Dec 2008 21:46:39 -0800 (PST) Message-ID: <7d6fde3d0812112146o28596b11vdf730f2b3afc9759@mail.gmail.com> Date: Thu, 11 Dec 2008 21:46:39 -0800 From: "Garrett Cooper" 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 05:46:40 -0000 On Thu, Dec 11, 2008 at 7:13 PM, 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? > > Beckman 7.x and 6.2 aren't ABI compatible, so unfortunately no, you have to babysit a bit. -Garrett