From owner-freebsd-ports@FreeBSD.ORG Thu Feb 7 14:32:49 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 9B08B16A46B for ; Thu, 7 Feb 2008 14:32:49 +0000 (UTC) (envelope-from hans@lambermont.dyndns.org) Received: from lambermont.dyndns.org (lambermont.dyndns.org [82.95.221.39]) by mx1.freebsd.org (Postfix) with ESMTP id 4799013C4EC for ; Thu, 7 Feb 2008 14:32:49 +0000 (UTC) (envelope-from hans@lambermont.dyndns.org) Received: by lambermont.dyndns.org (Postfix, from userid 1001) id 0846522DDF1; Thu, 7 Feb 2008 15:32:47 +0100 (CET) Date: Thu, 7 Feb 2008 15:32:47 +0100 To: Jeremy Chadwick Message-ID: <20080207143247.GB53709@leia.lambermont.dyndns.org> References: <1563a4fd0802052211h623de132q68a1ad0c8a9b930c@mail.gmail.com> <230174700802060040x4f2a0815r1a4bdc7fccf62b5d@mail.gmail.com> <20080206095133.GA94134@eos.sc1.parodius.com> <20080206110215.T2130@wojtek.tensor.gdynia.pl> <1563a4fd0802060239t16e539adn784001d75f9d1d02@mail.gmail.com> <20080206114113.GA95591@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080206114113.GA95591@eos.sc1.parodius.com> User-Agent: Mutt/1.4.2.3i From: hans@lambermont.dyndns.org (Hans Lambermont) Cc: freebsd-ports@freebsd.org Subject: Re: Upgrading the Installed package 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: Thu, 07 Feb 2008 14:32:49 -0000 Jeremy Chadwick wrote: ... > The way you upgrade a port/package on a FreeBSD machine is that you > pkg_delete (deinstall) the old one before pkg_add'ing (installing) the > new one. All package management systems on every platform I've used > (Solaris, Linux, and FreeBSD) behave this way. The dreadful RPM system does not work this way. It leaves the files that get no update untouched, adds new stuff next to them and then removes the obsoleted files. rpm -Uvv shows the upgrade behaviour : * Run %pre of new package (2) * Install new files * Run %post of new package (2) * Run %preun of old package (1) * Delete any old files not overwritten by newer ones * Run %postun of old package (1) > It would help if you could explain why you cannot afford to pkg_delete > your 1.0 package before installing 1.1. This is the interesting question ;-) regards, Hans Lambermont