Hi,

I'm looking for a solution to the following problem.

I have an engine library MySite which is a common base of code used to
build a new site upon.

Site1, Site2, and Site3 each have a copy of MySite at various stages in
development; the copies of MySite aren't always in a consistent state
because as I fix something or add a feature to the engine for a
particular site, I have to regression test it before running the other
sites against it.

I'm trying to figure out how to have three varying copies of MySite
under the same mod_perl server.  As far as I can tell, perl just uses
the first one it encounters.

I could rework things like putting MySite under Site1 (yielding
Site1::MySite::Foo) or renaming MySite for each site (yielding
MySite_Site1::Foo), but both of these methods aren't going to let me use
CVS on the live copies.

I could run a separate mod_perl server for each site using MySite, but
this eats up more memory and requires extra initscript handholding.

I had a fleeting thought about some kind of kludge in the startup script
for each site that would do something like the following:  read each
library file and application file into a string,
s/MySite/MySite_Site1/g, and eval the resulting string.  But I'm not
enough of a Perl guru to know whether that will work or not.

So I'm here soliciting advice.  I hope that was somewhat clear and that
I'm not crazy....

thanks,

-- 
Ryan Underwood, <[EMAIL PROTECTED]>

-- 
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html

Reply via email to