yeah, and then users have to repair broken ./configure scripts
again and again.
Really? How often does this actually happen? My experiences with autoconf have been pretty good down the years and they get better as people get better at using it. It's certainly not beyond criticism - it's a sprawling and somewhat non-obvious metalanguage for a developer to learn for a start - but it works OK.
Well, at this point we have no need to use autoconf time wasting autoconf anylonger. Instead we should maintain config stuff carefully by hand - I'd volounteer for this job.
Did we just go through a time warp? I thought we did this a month ago and decided it wasn't going to happen.
-- Andy Armstrong, hexten.net
