Simultaneous multiple module versions

[Toby Corkindale]

So, we're trying to port this ancient app to run on the same servers as some
modern apps.. The ancient app uses some ancient versions of modules, which have
since been changed in non-backwards-compatible ways.

I'd like to have multiple versions of the same modules installed, and used
selectively by different mod_perl apps on the same apache daemon... Horrible,
no?

Now, only.pm would let me select which version of a module to load, but I have
several apps loaded by mod_perl, and I *don't* want the others to be getting
this ancient version.. argh..

Options I've thought of so far:
a) Run multiple versions of the Perl interpreter within mod_perl (and almost
   double the memory footprint of apache..)
   (Or run multiple instances of apache with different @INC setup)
b) rename the old modules to Ancient::whatever and %s///g for references to
   them in the old app.
c) Give up on porting the app, and just shift disk images of the old RH7
   machines onto vmware machines running on new hardware and try to get the
   re-write priority raised.
d) Start drinking heavily.

Any thoughts or options I've missed?

thanks, as always,
Toby

-- 
Turning and turning in the widening gyre/The falcon cannot hear the falconer;
Things fall apart, the centre cannot hold/Mere anarchy is loosed upon the world
(gpg --keyserver www.co.uk.pgp.net --recv-key B1CCF88E)