Date: Tue, 28 Nov 2000 20:47:06 +0100 From: Szilveszter Adam <sziszi@petra.hos.u-szeged.hu> To: "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org> Subject: Re: pkg_version Message-ID: <20001128204706.A30695@petra.hos.u-szeged.hu> In-Reply-To: <7799D023E51ED311BFB50008C75DD7B402881AD7@uschiexc05.kweb.us.kpmg.com>; from jpasski@kpmg.com on Tue, Nov 28, 2000 at 02:20:09PM -0500 References: <7799D023E51ED311BFB50008C75DD7B402881AD7@uschiexc05.kweb.us.kpmg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 28, 2000 at 02:20:09PM -0500, Passki, Jonathan P wrote: > Hello, > > I have more of a 'best practice' question than anything relating to updating > installed programs. I've searched and seen related posts, but I couldn't > really find what I was looking for. When I do a package update, I usually > use pkg_version -c, which displays the commands needed to upgrade an > installed package, usually in the form 'cd /usr/ports/path/of/package; make > && pkg_delete -f <package>'... or sometimes 'make deinstall && make > reinstall' > > When trying to upgrade complex applications like XFree86 w/ Enlightenment & > Gnome, is there a sequence that should be followed on what applications are > updated first to last? Other than a Stop error, or while the package > realizes a component is missing, and it retrieves it, I have no idea if > there is a dependency issue I'm FUBARing, or if I'm screwing up a previously > installed application. > > Any and all insight is appreciated! Hi! When I am sure that all of them have actually changed, I usually work my way up on the dependency list from the bottom, eg I do X first. If this is just a patch, the order might not matter. I have never wondered much about this, because X is also a real pain to wait for on this system until it completes building so I schedule it first (preferably when I am not around) and do the light stuff (TM) later. Of course, if the shared library version number got bumped in the meantime and your new port requires that new version, your bets are pretty much off... the sequence is fixed then. (Same, if the number wasn't bumped but it should have been:-) Do not worry much about this, however, since if you really do it in the wrong order, you will notice it usually as the compile breaks... Got some practice just recently, when I had to recompile every port (and every other program too) because the libc version number got bumped in -CURRENT. It was fun:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001128204706.A30695>