Re: why is gtk install so difficult?



On Mon, 20 Oct 2003 14:29:05 EDT, Ruben Safir Secretary NYLXS said:

> IMO, That is all that should be needed to compile anything to a sane
> configuration.  How many places can the libraries be sitting? - 4 or 5
> tops?  Use locate in the autoconf file, or find if need be.

Umm. No.

locate is a bad choice - if the bozo has installed glib or something wrong, and
hasn't re-run the program to rebuild locate's database, you're just digging a
deeper "why doesn't this work" hole.

If you're so unsure about its location that you're resorting to 'find', you
just bought yourself a 'find /'.  Yes, over *all* the file systems.  Including
NFS.  Figuring out how to make automount filesystems DTRT (when they're
configured to automount /usr/local/borked-source on the fly but they aren't
mounted when the find runs, for example) is left as an exercise for the
masochistic reader.

I hate to say it, but GTK is *NOT* the most difficult thing in the world to
install. If you can't be bothered to read the directions and understand the
tools, maybe you need to make a decision:

1) whether to just wait for your vendor to provide .RPMs/.DEBs or whatever, or 
2) pay somebody with a clue to do it for you (may often not be more than
beer&pizza money) or
3) drive your own lame ass to the hospital to have the bullets removed from
your feet.

There's no reason to make the install process do anything more complicated than:
1) Pre-req packages correctly installed in /usr
2) Pre-req packages correctly installed in /usr/local
3) Pre-req packages correctly installed someplace that pkgconfig describes
properly.
4) Tell the user to look in config.log and get his system into a state
described by (1-3).




Attachment: pgpG52QqSKsb3.pgp
Description: PGP signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]