From owner-freebsd-ports Thu Feb 8 0:11:58 2001 Delivered-To: freebsd-ports@freebsd.org Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 2446437B401; Thu, 8 Feb 2001 00:11:41 -0800 (PST) Received: from mira1.cisco.com (mira1.cisco.com [171.71.208.193]) by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id AAA04496; Thu, 8 Feb 2001 00:11:54 -0800 (PST) Received: from cisco.com (ptlm1-dhcp-113.cisco.com [171.71.210.113]) by mira1.cisco.com (Mirapoint) with ESMTP id AAI01683; Thu, 8 Feb 2001 00:11:39 -0800 (PST) Message-ID: <3A82547E.18AD4D26@cisco.com> Date: Thu, 08 Feb 2001 00:10:38 -0800 From: W Gerald Hicks Organization: Cisco Systems, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: bmah@FreeBSD.ORG Cc: ports@FreeBSD.ORG, Kal Torak Subject: Re: Ports updating... Good ways? References: <3A8208E7.C6EE4C24@quake.com.au> <20010208061814.5E6C5E6A17@netcom1.netcom.com> <200102080638.f186c9s39260@bmah-freebsd-0.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [redirected to ports] (Hi Bruce :-) In thinking about this further, it seems to me there is also some missing metadata that one would need to automate port upgrades reliably. There doesn't seem to be anything that relates previous versions of a port to an updated one. At least not in a rigorous manner that could be trusted by naive scripts... Cheers, Jerry Hicks gehicks@cisco.com "Bruce A. Mah" wrote: > > Trying to impart some UI: > > Akinori MUSHA has an experimental tool to do ports upgrading at: > > http://people.FreeBSD.org/~knu/misc/portupgrade.tar.gz > > Also, see pkg_upgrade in -CURRENT. > > I haven't played with either of these (yet). > > Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message