Re: Re: Thoughts on script portability

you can BEGIN { unshift @INC, "/path/to/Modules"; } on all your scripts

Actually had a case where that didn't work either. The hosting site had set the CGI environment in such a way that it could not see outside of a very limited environment similar to a chroot environment in Unix. Other than d:\path\perl or e:\cgi-bin was invisible.

Peter L. Berghold -- Unix Professional Peter at Berghold dot Net
	Dog trainer, dog agility exhibitor, brewer of fine Belgian style ales. Happiness is a warm, tired, contented dog curled up at your side and a good Belgian ale in your chalice.

Comment on Re: Re: Thoughts on script portability Download Code

Replies are listed 'Best First'.
Re: Re: Re: Thoughts on script portability by Vautrin (Hermit) on Jan 24, 2004 at 23:54 UTC
Even if you are jailed (chrooted) into the CGI directory you should still be able to create a directory (even over FTP -- unless the servers are so locked down that you can't even upload files ;-D), and then use "./modules" (or whatever) as the path to the modules. Of course, that's on a Windows, server, correct? Hmmmm. I suppose worst case scenario you could just keep all the modules in the current directory.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Thoughts on script portability
by Vautrin (Hermit) on Jan 24, 2004 at 23:54 UTC

Even if you are jailed (chrooted) into the CGI directory you should still be able to create a directory (even over FTP -- unless the servers are so locked down that you can't even upload files ;-D), and then use "./modules" (or whatever) as the path to the modules. Of course, that's on a Windows, server, correct? Hmmmm. I suppose worst case scenario you could just keep all the modules in the current directory.

[reply]