So, I'm thinking of installing bricolage to manage my website, which currently runs Apache 2.0. Debian/stable doesn't include Apache 2, so I have to build it from source. So far no problem.

Bricolage requires mod_perl, so off I trot to go and build that. If using Apache 2, apparently I have to use mod_perl 2.0. This is currently in prerelease (as a 1.99-something release), and only compiles as a shared library (DSO).

Bricolage requires that it be compiled statically. Grrr.

Looks like I'm going to have to reinstall Apache 1.3 in order to get this working, which will break Subversion, which requires Apache 2.0. Moreover, going back to Apache 1.3 will probably break my virtual host configuration, requiring more work.

Feck.

I like Apache 2.0 but hate that it is incompatible with everything that ran with 1.x
What happend, did the apache team get an influx of ex-microsoft developers?

I've got the same trouble. I would prefer to upgrade to Apache 2.0 but PHP recommends that you only use it with 1.3.x.
A lot of things just plain don't work in Apache 2.0 which is very annoying but since everybody is told to only use 1.3.x then the push for 2.0 is slow.

AOL. I went to 2.0 and had to go back to 1.3 because not all the modules I need were supported.

Looks like I'm going to have go back to 1.3. Since I want to run 2.0 to play with Subversion, I'll have to run 2.0 on a different port, and use mod_proxy to redirect chunks of the 1.3 namespace to it.

All of which means that I'll have to be extremely careful about not breaking my virtual hosts and CGI setup.