> I don't think how Apache is [cC]onfigured should hold anyone up as
> far as working on 2.0. We've been able to handle just about any
> configuration desire or need up to now, and I tend to think that
> we'll continue to be able to do that. Just that the idea of a "total
> rewrite from the ground up" stalled development of 2.0, so does
> the idea that "we need to scrap what we have for autoconf." I'm
> not saying that anything one way or another re: autoconf, just
> stating the facts :)
Yikes! I would really really hate to see the current configuration scheme
migrate into the 2.0 release. Perhaps enough that I would sit down and
get an automake/libtool/autoconf system up and going.
-Rasmus
|