From owner-freebsd-ports Wed May 26 16: 2:24 1999 Delivered-To: freebsd-ports@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id 1F168158B3 for ; Wed, 26 May 1999 16:02:21 -0700 (PDT) (envelope-from patl@phoenix.volant.org) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with smtp (Exim 1.92 #8) id 10mmgm-0001u2-00; Wed, 26 May 1999 16:02:20 -0700 Received: from localhost by asimov.phoenix.volant.org (SMI-8.6/SMI-SVR4) id QAA10976; Wed, 26 May 1999 16:02:15 -0700 Date: Wed, 26 May 1999 16:02:15 -0700 (PDT) From: patl@phoenix.volant.org Reply-To: patl@phoenix.volant.org Subject: Re: Right way to upgrade a port To: Chris Piazza Cc: Oscar Bonilla , ports@FreeBSD.ORG In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > p.s. wouln't it be cool if you could install on top of the old version > > and later remove the new version just to find out that the old version > > still works. :) > > I have a feeling that that would require a lot of hard drive space for > backups :-). There could be the odd chance that would work. Say, if the > new version installed everything in a different place! It would work fine if pkg_delete were just a little bit smarter so that it wouldn't delete any file that is also used by another installed package. The problem with the pkg_delete/make install sequence is that it can get quite awkward if there are other ports that depend on the one you are trying to update. For worst-case scenaria, check out the dependancy trees for gnome and kde... -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message