Ok, I know you're not supposed to do it, but I'm needing to try. The plan:
Slash 2.0 is under /usr/local/slash, version 2.2 will be under
All perl modules will go under /usr/lib/perl5/site_perl/5.6.0/slash22
Will have two instances of httpd running, one with a modified apachectl that
will set the PERL5LIB var to the above directory and use an alternate config
file. (I think I'll use the exact same httpd executable for both, but they
will run seperately.)
I have a spare IP address, so I'll have the 2.0 httpd listen on one and the
2.2 httpd on another.
Actually the only problem I'm having right now is that when I do 'make' in
the 2.2 directory, it is clobbering my old installed Slash 2.0 modules.
(This is on my home test box, not the server! And they can be restored by
going to the 2.0 dir and doing make and make install, and the old site comes
back up fine.)
In the 2.2 Makefile I made these changes:
# INSTALLSITEARCH=`$(PERL) -MConfig -e 'print
# INSTALLSITELIB=`$(PERL) -MConfig -e 'print
I noticed later that those are only used for RPM builds. I'm not using RPM.
So how do I get the installer to put the modules in the right place?
Like to travel? http://TravTalk.org
Micah Yoder Internet Development http://yoderdev.com
Get latest updates about Open Source Projects, Conferences and News.