Re: Upgrading mod_perl on production machine (again)

2001-01-20 Thread Honza Pazdziora
On Fri, Jan 19, 2001 at 12:09:54PM -0800, rolf van widenfelt wrote: but, if someone can offer a procedure for setting up two independent httpd+modperl+perl environments on one machine it would be pretty interesting! You can do that but have to give up installing _anything_ into /usr/lib or

Re: Upgrading mod_perl on production machine (again)

2001-01-19 Thread rolf van widenfelt
face it, you are trying to perform surgery on a live subject... with all the Makefiles you'll be making, (httpd, modperl, perl...) you're bound to slip on one of them and install over some of your existing stuff. i went thru a conflict like this once, and avoided it by simply getting a second

Re: Upgrading mod_perl on production machine (again)

2001-01-19 Thread Marc Spitzer
- Original Message - From: "rolf van widenfelt" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: "Bill Moseley" [EMAIL PROTECTED] Sent: Friday, January 19, 2001 3:09 PM Subject: Re: Upgrading mod_perl on production machine (again) face it, you are trying to perform surge

Upgrading mod_perl on production machine (again)

2001-01-16 Thread Bill Moseley
This is a revisit of a question last September where I asked about upgrading mod_perl and Perl on a busy machine. IIRC, Greg, Stas, and Perrin offered suggestions such as installing from RPMs or tarballs, and using symlinks. The RPM/tarball option worries me a bit, since if I do forget a file,

Re: Upgrading mod_perl on production machine (again)

2001-01-16 Thread Greg Cope
Bill Moseley wrote: This is a revisit of a question last September where I asked about upgrading mod_perl and Perl on a busy machine. IIRC, Greg, Stas, and Perrin offered suggestions such as installing from RPMs or tarballs, and using symlinks. The RPM/tarball option worries me a bit,

Re: Upgrading mod_perl on production machine (again)

2001-01-16 Thread Steve Reppucci
Not that I have an answer to this complete problem, but I have had similar situation, so I'll also be interested in the solutions you uncover. I've always handled the support of multiple perl versions by installing new versions of perl using a prefix like /usr/local/perl/5.6.0, etc., (I also

Re: Upgrading mod_perl on production machine (again)

2001-01-16 Thread David McCabe
From: Steve Reppucci [EMAIL PROTECTED] Date: Tue, 16 Jan 2001 11:02:44 -0500 (EST) Subject: Re: Upgrading mod_perl on production machine (again) I've always handled the support of multiple perl versions by installing new versions of perl using a prefix like /usr/local/perl/5.6.0, etc., (I

Re: Upgrading mod_perl on production machine (again)

2001-01-16 Thread Perrin Harkins
The RPM/tarball option worries me a bit, since if I do forget a file, then I'll be down for a while, plus I don't have another machine of the same type where I can create the tarball. There's no substitute for testing. If it's really important to have a very short down time, you need a

Re: Upgrading mod_perl on production machine (again)

2001-01-16 Thread brian moseley
On Tue, 16 Jan 2001, David McCabe wrote: From: Steve Reppucci [EMAIL PROTECTED] I've always handled the support of multiple perl versions by installing new versions of perl using a prefix like /usr/local/perl/5.6.0, etc., (I also place CPAN's build directory under that tree.) That