Scripting and Gnome and KDE

[Jody Winston]

Karl EICHWALDER <ke at gnu.franken.de> writes:

> Andrew Kuchling <akuchlin at mems-exchange.org> writes:
> 
> > Then reality sets in: GNOME uses patched versions of all sorts of
> > things such as automake, but this is never clearly documented
> > anywhere.
> libtool might be an exception.  But normally it's enough to use recent
> versions of all involved tools.
> 
> > There's a large pile of libraries, and it's not clear which ones are
> > needed and which ones are obsolete;
> 
> autoconf resp. ./configure is considered to do all needed checks for
> you.  If it fails for some reason it's a bug; please, report it.  We'll
> try to improve the check and add a note to the README file.
> 
> The problem is, it works nicely for the devolopers and package makers
> (like me) who are familiar with the progress GNOME makes.
> 

I have to agree with Andrew because I have had these problems and
more.  I don't work on a Linux machine, but an SGI.  It was very
difficult to get the libraries that GNOME needs to work to run.  I
finally gave up on GNOME.  These problems are not just with GNOME and
its assorted libraries but with other Open Software tools such as
gimp.

I've been building and using Open Software since 1982 on all sorts of
platforms.  I've been using and devloping on Linux for over 5 years.
This includes several commercial applications (Visual Shell, Digital
Analysis for Pipeline corrosion and deformation) and custom device
drivers (stepper motors, ccd camera controller).

It looks like to me that we have gone back to the model that all the
world is a Vax and if it compiles and runs on the Vax there isn't any
problem with the software.  All the world isn't Linux and the only
compiler isn't gcc.

-- 
Jody Winston