Date: Wed, 1 Oct 1997 08:45:57 -0400 (EDT) From: Jamie Bowden <jamie@itribe.net> To: chat@freebsd.org Subject: Re: Microsoft brainrot (was: r-cmds and DNS and /etc/host.conf) Message-ID: <199710011243.IAA03581@gatekeeper.itribe.net> In-Reply-To: <199710010554.WAA21894@kithrup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 30 Sep 1997, Sean Eric Fagan wrote: > In article <Pine.BSF.3.96.971001002405.289D-100000.kithrup.freebsd.chat@journey2.mat.net> you write: > >OK. You mean this (I guess, from above) that this includes the ports > >packages. One shortcoming of ports is that the packages aren't aware of > >the sensitivities involved in upgrading from one version to a newer > >version of a package. port A, when going from version A.1 to A.2, simply > >writes a new package, A.2, right besides A.1. A later pkg_delete of A.1 > >will wipe out A.2's functionality. > > This is something I do at work -- making sure that it is possible to upgrade > the OS without having to shut down. (There's a reboot to get to the new > kernel, of course.) > > This is *hard*. Mainly because nobody bothers writing support for it ;). The way I deal with this is something borrowed from someone else (of course). My /usr/local is full of /usr/local/foo-1.1, whith foo-1.1 having it's bin, sbin, etc, lib, etc. /usr/local/bin is full of softlinks to /usr/local/foo-1.1/bin/*, /usr/local/lib to /usr/local/foo-1.1/lib/*. When I compile and install a new version of foo, it gets installed to /usr/local/foo-2.0. I still have my original intact, and only need update the softlinks to update the program from a user standpoint. And of course, we also borrowed the perl script that was written to do all this. It's not perfect, but I don't have the problem of having unknown files from random software laying around. Jamie Bowden System Administrator, iTRiBE.net Abusenet: The Misinformation Superhighway
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710011243.IAA03581>