From owner-freebsd-ports Sun May 13 7:46:43 2001 Delivered-To: freebsd-ports@freebsd.org Received: from hub.lovett.com (hub.lovett.com [216.60.121.161]) by hub.freebsd.org (Postfix) with ESMTP id 0B31737B43E for ; Sun, 13 May 2001 07:46:41 -0700 (PDT) (envelope-from ade@lovett.com) Received: from ade by hub.lovett.com with local (Exim 3.22 #1) id 14yx6h-0001Qc-00; Sun, 13 May 2001 09:44:27 -0500 Date: Sun, 13 May 2001 09:44:27 -0500 From: Ade Lovett To: =?iso-8859-1?Q?Joachim_Str=F6mbergson?= Cc: ports Subject: Re: gnomeui.so.4 (was: Re: gnome 1.2 & gnomecore 1.4??) Message-ID: <20010513094427.A403@FreeBSD.org> References: <3AF9B430.DF487472@home.com> <20010510092821.G6932@FreeBSD.org> <3AFD3840.14FBE991@ludd.luth.se> <20010512101336.B617@FreeBSD.org> <3AFE944E.D56E1AC9@ludd.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <3AFE944E.D56E1AC9@ludd.luth.se>; from watchman@ludd.luth.se on Sun, May 13, 2001 at 04:03:58PM +0200 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, May 13, 2001 at 04:03:58PM +0200, Joachim Strömbergson wrote: > BTW is there any way to make ld report what file(s) are causing the > loading of a certain module? Right now I get what file it can't find, > but if I could get the info about the program that tried to call > gnomeui.so.4, it would be possible to backtrack the port I need to > update. man ldd > This on the other hand is a well engineered system that should be and > normally is upgradeable, manageable and generally made to operate for > years without needing the wipeout measure now and then. No, the current ports/package system is, whilst well engineered within its limitations, generally unable to deal with anything apart from relatively trivial upgrades. x11/gnome comprises some 70-odd ports that all need to be kept in sync with each other, or bad things will happen. This doesn't include all the other GNOME ports that may be floating around on the system, which also need to be removed and recompiled. > If your only tool is a hammer, then treating every problem as a nail > might be ok. But if your only tool is a thermonuclear missile, then you > should think both once or twice of alternative solutions before nuking > away... Go and read the archives of this list, where magical upgrade tools have been discussed many, many times, then send in a PR with the necessary patches to make upgrading huge ports (like GNOME and KDE) trivial. I'll make you famous. -aDe -- Ade Lovett, Austin, TX. ade@FreeBSD.org FreeBSD: The Power to Serve http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message