NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Small addition: Set dynamic path to the toolchain (Score:1)
I keep meaning to contribute the following .bat file which sets up the environment for a console dynamically. This first snippet can be called from any .cmd file or from within cmd.exe:
Another thing - you provide only a .exe file - I found it very convenient to also have a .zip file which does not try installation into write-protected directories like anywhere on c:\ - if it's not too much hassle, it would be great if y
Re:Small addition: Set dynamic path to the toolcha (Score:1)
Perl 5.10.0 changes that a bit, and although the initial release of Strawberry 5.10.0 will be hard-coded as well, we'll look at making it movable after release.
HOWEVER, one advantage of moving beyond a config-file driven methodology is that it opens the door to a "Perl from Scratch" idea, where if you want a Perl that installs to a certain place you might, for example do the following. perldist would grind away silently for about an hour, and spit out an installer for Strawberry tailored to install to the directory you want.
Reply to This
Parent
Re: (Score:1)
"Hardcoded into Perl" on Win32 just means patching Config.pm respectively Config_heavy.pl, so the "it has to be done that way" can be remedied by a oneliner to change the installation path. @INC is built dynamically on Win32 anyway, so if you're not using CPAN or the toolchain, you don't even need to mess with Config.pm, Config_heavy.pl or CPAN/Config.pm at all.
Re: (Score:1)