On Thu, Dec 30, 2004 at 09:25:51AM -0800, John Eaton wrote: > So gEDA requires that your system has package Foo installed. Your distro > has Foo but > it is kept in a different location than the default used by Foo's > developers. gEDA installs > and runs ok. > > One year later there is a new gEDA that requires the latest rev of Foo. > Your original won't > work. So you grab the latest foo from foo.org, install it and wonder why > the new gEDA > still complains that you have the older version of Foo and won't run.
Yes. This happens when gEDA README forgets to say that the path to the newly installed lib should be explicitly passed. > Typical day in the life of anyone that does system administation but > this will stop an end user If I had problems with say GTK, I would 1) locate gtk 2) move everything that looks like GTK into /trash while maintaining the original directory structure 3) Download the latest GTK 4) Doing what they say in README 5) If some app gets broken, do 1)-4) for the app. I am maintaining my *end user* workstation this way and it seems to be one order more reliable than all the distributions. For example some guy who was trying to use gEDA on Fedora core 3 showed how gtk on startup complains about missing library module. And also demonstrated they have installed gtk into pkg-config wrong. They installed pkgconfig into /usr and gtk into /usr/local (or the other way) and forgot to set up PKG_CONFIG_PATH in /etc/profile. I don't have problems with gtk nor pkgconfig on my compiled system. It works just fine. I just downloaded pango, atk, glib, gtk as they said in README, compiled, and voila, GTK was here. Without problems caused by some third party people between me and GTK. Why to try accomodate for something that third party people made when it just brings more problems? Don't you have enough problems on gEDA development already? Cl<
