-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Let's take a typical autoconf package. I'll call it package-xyz. Joe GNU/Linux User has just downloaded and untared this package. Like most users, the first thing he does is change directory to the newly-unpacked source tree and run a quick "ls" to see what files are there. To his delight, he discovers a "configure" script, indicating that he probably doesn't have to do any editing of Makefiles or other such craziness. Little does he realize the troubles awaiting him.
He again does the typical thing and runs "./configure --prefix=/opt". The configure script runs for a while, then exits with an error which basically translates to "You have an autoconf version which is three weeks old; please upgrade", but this is displayed in the most cryptic manner possible. He won't realize this is indeed what the error message means until he runs a few quick Google searches. He really wants to install this program, so he doesn't give up quickly. A few minutes later, he's run apt-get upgrade (or run whatever auto update his distribution uses). full article plus comments. http://freshmeat.net/articles/view/889/ - -- all the things we keep inside, are the things that really matter, the face puts on its best disguise, and all is well, until the heart betrays. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/E/207v3NbZTFJeIRAo2qAKCvRJO0Y0Z1itm+jzCpLRqkr7qRnwCdEFME QiJhG34IdlUd+phhNu2/nXA= =Kurc -----END PGP SIGNATURE----- _______________________________________________ ilugd mailing list [EMAIL PROTECTED] http://frodo.hserus.net/mailman/listinfo/ilugd
