Hi Dom -- > How do you cope with the problem that perl has of running different > versions of modules? > > 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.
The short answer: PERL5LIB Read my earlier messages in this thread. In one I describe the layout of my site architecture which fully accommodates this reality. In a nutshell, each site has its own "modules/" directory in which ALL the modules for a project, including CPAN libraries, are stored. The environment variable PERL5LIB can be set separately for each virtual host (Apache directive "SetEnv" and "PerlSetEnv" for mod_perl users), thereby allowing each site to have its OWN versions of libraries. If you isolate your web site from the host operating system you will gain significant freedom and ease of management. Warmest regards, -Jesse- -- Jesse Erlbaum The Erlbaum Group [EMAIL PROTECTED] Phone: 212-684-6161 Fax: 212-684-6226
