From owner-freebsd-hackers@FreeBSD.ORG Mon Oct 15 00:06:40 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E58BA16A420 for ; Mon, 15 Oct 2007 00:06:40 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd2mo1so.prod.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id A393E13C455 for ; Mon, 15 Oct 2007 00:06:40 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from pd4mr2so.prod.shaw.ca (pd4mr2so-qfe3.prod.shaw.ca [10.0.141.213]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JPX00A1RC4XS460@l-daemon> for freebsd-hackers@freebsd.org; Sun, 14 Oct 2007 17:05:21 -0600 (MDT) Received: from pn2ml3so.prod.shaw.ca ([10.0.121.147]) by pd4mr2so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0JPX009YQC4YV240@pd4mr2so.prod.shaw.ca> for freebsd-hackers@freebsd.org; Sun, 14 Oct 2007 17:05:22 -0600 (MDT) Received: from soralx ([24.87.3.133]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0JPX0016JC4XURX0@l-daemon> for freebsd-hackers@freebsd.org; Sun, 14 Oct 2007 17:05:21 -0600 (MDT) Date: Sun, 14 Oct 2007 16:05:20 -0700 From: soralx@cydem.org In-reply-to: <20071014203736.GB2677@lava.net> To: cliftonr@lava.net Message-id: <20071014160520.07ad521d@soralx> MIME-version: 1.0 X-Mailer: Claws Mail 3.0.2 (GTK+ 2.10.14; i386-portbld-freebsd6.2) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit References: <20071014203736.GB2677@lava.net> Cc: freebsd-hackers@freebsd.org Subject: Re: A more tenuously package-related question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Oct 2007 00:06:41 -0000 > I used to use pkg_update from the 'pkg_install-devel' toolset to > upgrade systems via replacement of binary packages. Its > implementation had some minor flaws - it was essentially a perl > wrapper for an iterative "pkg_delete -f" followed by "pkg_add -f", > which made it problematic to upgrade either the perl or pkg_install > packages, for instance - but the core idea was excellent. Despite > those flaws it was very useful in maintaining servers via binary > packages, because it would reconnect the pkgdb dependencies on the > old package version to the new package version. However, it's not > part of the current base package tools. > > Is there any better equivalent tool at the moment, or should I just > resuscitate the old "pkg_update"? Did you try ports-mgmt/portupgrade? You can run it as `portupgrade -P` for binary updates. Besides actual 'portupgrade', it has a set of useful tools, too. But be warned -- the utility is snail-slow. > -- Clifton [SorAlx] ridin' VS1400