in reply to Developement and production mod_perl sites on a single server
You need to run two separate servers. There's no other clean way around it.
We keep all of our web code, including configuration, in CVS. The same Apache installation is hard-coded into configuration, but the rest is left relative to a server-root, which is dynamically replaced at startup time (as is the port; hard to run all servers on the same port). The startup script also takes care of setting PERL5LIB, the easiest way to reassign library paths to development libs (since it unshifts the paths onto @INC rather than pushing them). Since our CVS hierarchy mirrors our production hierarchy, our "production" environment is just another checkout of our CVS code. We actually use this to setup multiple development environments, so that each of our developers can run their own "personal" web servers.