Date: Thu, 7 Feb 2008 15:32:47 +0100 From: hans@lambermont.dyndns.org (Hans Lambermont) To: Jeremy Chadwick <koitsu@freebsd.org> Cc: freebsd-ports@freebsd.org Subject: Re: Upgrading the Installed package Message-ID: <20080207143247.GB53709@leia.lambermont.dyndns.org> In-Reply-To: <20080206114113.GA95591@eos.sc1.parodius.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080207143247.GB53709>