Date: Wed, 29 Nov 2000 10:59:35 -0500 From: "Passki, Jonathan P" <jpasski@kpmg.com> To: "'freebsd-stable@freebsd.org'" <freebsd-stable@freebsd.org>, "'freebsd-ports@freebsd.org'" <freebsd-ports@freebsd.org> Subject: RE: pkg_version Message-ID: <7799D023E51ED311BFB50008C75DD7B402881AEC@uschiexc05.kweb.us.kpmg.com>
next in thread | raw e-mail | index | archive | help
Thanks for all with the feedback on this. After doing an unsuccessful port upgrade (thanks for the info, but I managed to FUBAR my installed ports anyways :), I'm faced with a similar problem. <rant> Of all the understanding and interaction I do with FreeBSD, this one issue, the issue of a seamless (or semi-seamless) upgrade of installed ports seems to be the one I have never seen a consistent solution with. Given my lack of port understanding, I have no right to criticize something that I wouldn't know how to fix, but doesn't it seem odd that upgrading applications like this are difficult or esoteric to many people (search archives, the question keeps on coming up). Also, when people approach me about the port upgrade procedures, and ask if it's better than Debian's, I tend to say it isn't. I love the ports, and I appreciate all the effort people have put into porting applications and package install procedures, but... Maybe it's just the nature of installed ports that make them so difficult to upgrade, but it's still for me, a pain when there are so many dependencies (usually XFree86 + window manager + apps related to window manager), and not knowing what ones to do in what order, and one utility that can do all this. There's a pkg_add(1), pkg_create(1), pkg_delete(1), pkg_info(1), and a pkg_version(1), but not a single utility that should be called pkg_upgrade, which does it with the most reduced effort possible </rant> Feel free to flame, I put on the fire retardant suit when I wrote this :) I'm blaming most of this on myself for perhaps a lack of understanding, but there have been many before with the same question. Also, wouldn't this be good advocacy to house a more robust port system? Thanks for your ear, Jon > -----Original Message----- > From: John Reynolds~ [mailto:jreynold@sedona.ch.intel.com] > Sent: Wednesday, November 29, 2000 09:39 > To: 'freebsd-stable@freebsd.org' > Subject: Re: pkg_version > > > > [ On Tuesday, November 28, Szilveszter Adam wrote: ] > > > > 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 > > Is there some sort of "recursive 'make deinstall'" that will > delete a package > and everything it depends on to run or build? > > i.e. if I wanted to nuke all of GNOME, if I do: > > cd /usr/ports/x11/gnome && make deinstall > > all that will do is delete the "port" for GNOME (which simply > pulls in all the > other ports accordingly) but doesn't deinstall the > components. How could one > remove all components of GNOME even down to the libraries (I know some > libraries would be needed by other ports)? > > I've done this before "manually" but it was certainly tedious. > > -Jr > > ***************************************************************************** The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing KPMG client engagement letter. ***************************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7799D023E51ED311BFB50008C75DD7B402881AEC>