Re: Raggin' on auto*
> How often did you try to write a config
> script? I tried two times but each time
> I had big problems. Last time I tried to
Well, y'know, that's why they pay us computer
programmers the big bucks -- to figure sh** like that
out. You sound like one of those whiner web
weenies who think that slinging HTML is
"programming". It's not. Programming is work. Part of
the work is
learning the tools. 'autoconf' is a hairy tool, but it
works, and works well. 'automake'.... well, the less
said there the better, I do not use it and refuse to
use it, because my code must be portable across
multiple operating systems, including those upon
which 'autoconf' is not installed.
So, good luck with learning Linux. Maybe in a few
years you'll know enough to know the difference
between an 'autoconf' problem and an 'automake'
problem. And BTW, the dependencies issue doesn't
belong to either tool -- that's a Linux (and Unix in
general) problem, where OS venders keep
changing where they sling things. Don't blame
'autoconf' for things it's not responsible for.
> coherent form, preferably using sane
> tools (who the hell uses m4?).
I used to generate my entire web site via a complex
set of m4 macros. Not my fault if you're not geek
enough to do that :-).
> It would also be nice if there was a GUI
> option so less experienced people could
> install without having to use the
There is such a tool. It is called 'krpm' or 'gnorpm',
my friend. Less experienced people should not be
messing with source code, and shouldn't even
know what a compiler *IS*, much less be invoking