Rob Nagler wrote:
How do you cope with the problem that perl has of running different versions of modules?Another approach which allows easy sharing between projects is:~/src/perl/ + Project1/ + Project2/ + Project3/ where Project[123] are root package names. Set PERLLIB=~/src/perl and you can get access to any *.pm in the system, each has a globally unique name. This makes it easy to implement cross-project refactorings.
We have a similiar situation, in that we're running several projects with different sets of perl libraries. We have common code between them. The trouble starts when we're running several sites on the same virtual server. At that point, there's only one copy of the canonical code running, rather than each vhost getting its own copy.
I realise that this is usually what's wanted, but it can make life very difficult when you're trying to upgrade one vhost, which needs a new version of one of the shared modules because you might break one of the others by accident. I haven't found a good solution to this yet...
-Dom
--
| Semantico: creators of major online resources |
| URL: http://www.semantico.com/ |
| Tel: +44 (1273) 722222 |
| Address: 33 Bond St., Brighton, Sussex, BN1 1RD, UK. |
