Re: Generic Programming and C++ Lib Standardization
That might be very well the case. But currently (as in version 1.30.2) there is no clean way how to install the thing.
If you search a little in some newsgroups you will find a lot of pleas for help. So what I will do now is copy libraries to /usr/local/lib till my compiler is satisfied.
Welcome back to the stone-age...
Re: Raggin' on auto*
did you read the article?
I guess you didn't want to flame and so do I.
If you compile your projects you have less problems with dependencies (compared to rpm).
However the problems are all for real. 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 add a new directory but it was not used because I did not include it in the configure.in file. No warnings there, no documentation.
All problems (non standart options, not noticed depenencies, no backward compatibility, ...) are human errors, but these errors are made because the whole process is so hard to understand.
In the end I think that the configure scripts are a good thing. Being so paranoid is a good thing. Ever tried to compile gimp on a SGI or on a Sun where you didn't have root privileges?
But we need to improve it. Better documentation, less complexity.