On Sun, 5 Aug 2001, Stas Bekman wrote:
> I understand that. I was suggesting something like
>
> PerlOptions +Inherit
>
> So you don't have to explicitly configure each vh, which can be
> cumbersome if you have many vhs use the same modules, but a few ones which
> are different. I'm talking about configuration flexibility and I
> understand that if you want a separate interp it won't share the code with
> another interp from a different pool.
i suppose we could have a PerlOption for that. but at the moment it isn't
too much trouble to have .pl files that pull in the desired modules. so
for example:
<VirtualHost foo>
PerlSwitches -MFoo -MBar standard_modules.pl
</VirtualHost>
<VirtualHost baz>
PerlSwitches -MBaz -MBiz standard_modules.pl
</VirtualHost>
> Is this a problem, because it's not easy to replicate a Perl interpreter
> with everything in it? and you always have to start a fresh interpreter if
> you want a new independent one?
the interpreter needs to be built from scratch if you want a vhost to have
different versions of a module.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
