Re: Moving Perl from test to Dev

If your test environment and your development environment are on the same box, you have a problem. Either they use the same perl (not desirable, otherwise you can't upgrade/replace the perl in one place, while not touching the other), or you have them at different locations. But then your test environment is different from your development environment, and that's far from ideal as well.

I strongly recommend against that. Otherwise, you might be able to get away with just reconfiguring/compiling/installing perl, and copying the locally installed modules. Or you might want to search for 'relocatable perl's. It seems to work on some OSses (OS/2 for instances), and some people (Redhat?) have success with configuring perl with a huge default @INC, and a binary edit of Perl. I don't think perl relocation is officially supported though.

Abigail

Comment on Re: Moving Perl from test to Dev

Replies are listed 'Best First'.
Re: Re: Moving Perl from test to Dev by ccarden (Monk) on Nov 20, 2003 at 19:52 UTC
But then your test environment is different from your development environment, and that's far from ideal as well. This is an excellent point. I've been in situations, though, where the development site did not have a budget that would allow for even one extra system to use as a test environment. It was definitely not the ideal situation.	[reply]