Everything is installed under "c:\strawberry-perl". Right now, directories are hard-coded at compile time, so users can't be given the option for where to install it. Soon, Perl will support a "relocatable @INC" with relative paths. See "Poll: Is your $^X an absolute path?" for some discussion.
There's been a request or two for a version of Strawberry that gets installed to "c:\perl" to seamlessly replace ActiveState installs, but I'd rather wait for 5.8.9 and let people install it wherever they want.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
| [reply]
[d/l] |
That's very good to know. I get that this is alpha software, and that there are good reasons not to be able to choose installation paths right now; however, I'd still suggest that in your next release you tweak the installer to tell me "Ready to install into C:\Strawberry-Perl" or some such.
Having now installed and played with it a bit, I noted one other thing that made me glad I'm so careful with pre-release software: even when running Strawberry Perl's perl.exe, my $ENV{PERL5LIB} is "C:\Program Files\ActiveState Perl Dev Kit 6.0\lib\". Fortunately, I didn't put Strawberry Perl in my path by default, but launch it from a Windows .CMD file, so was able to fix the issue:
@ECHO OFF
REM sperl.cmd - use Strawberry Perl for this session
C:\strawberry-perl\perl\bin\perl -x -S "%0" %*
goto ENDOFPERL
#!perl
#line 6
$basePath="C:\\strawberry-perl\\perl";
local $ENV{Path}="$basePath\\bin;".$ENV{Path};
local $ENV{PERL5LIB}="$basePath\\lib";
system($^X, @ARGV);
__END__
:ENDOFPERL
This is simple, and works on my system; I'm not sure it would work for everyone else. (And yes, I know that this isn't fixable, really, on your end -- ActiveState sets that env. var. during their install process.)
| [reply]
[d/l]
[select] |