Re: shebang I18N and apache

Honestly? Don't use non-7-bit-ascii characters in your path. "Doc, my arm hurts when I lift it this high." "Then don't lift it that high."

It may work for some things, but, really, is it that important what your directory structure is when compared to actually getting your CGI scripts working?

Comment on Re: shebang I18N and apache

Replies are listed 'Best First'.
Re^2: shebang I18N and apache by nicr (Initiate) on Feb 03, 2005 at 00:28 UTC
It sure would make life easier if we could figure out a way of getting this working...	[reply]
Re^3: shebang I18N and apache by Corion (Patriarch) on Feb 03, 2005 at 07:30 UTC
You will be in for more hurt than is worth the effort I fear. The File::Spec module splits the path (on Win32) on `\x5C`. I think you will need to recompile your Perl in a way that it uses forward slashes in all its configuration parameters, and you will need to patch at least File::Spec. I've recently learned that CPANPLUS also does not use File::Spec, and I assume that there are other modules that don't use it, but still perform path manipulation, so you will possibly need to patch these as well; maybe you are lucky though and the modules performing path manipulation are unix-centric and thus think that the forward slash is the measure of all things and spaces in filenames are forbidden. A smallish hack might be to edit the main `Config.pm` of Perl and change all paths there, but I think you need to patch the Perl.exe binary as well and "fix" all paths there too.	[reply]
Re^4: shebang I18N and apache by nicr (Initiate) on Feb 03, 2005 at 18:49 UTC
Thanks for the response. Now that I have a better understanding of why this is failing I guess that you may be right re: "You will be in for more hurt than is worth the effort...". Sounds like this might just be one big can of worms! cheers, nic	[reply]