use Perl

• Installing into locations other than C:\strawberry (Score:1)

  by Corion (7288)

  I still don't see where the difficulty is [perl.org]. You can skip the "Set up $ENV{PATH}" step in the setup for other locations (like, say, C:\Program Files\Strawberry Perl) and supply a batch file that sets up a "Perl Console" which has the correct $ENV{PATH}:

  @echo off
  SET BASE=%~dp0
  path %BASE%\perl\bin;%BASE%\mingw\bin;%BASE%\dmake\bin;%PATH%
  echo "Strawberry Perl Console launched."
  %COMSPEC%
  • Re:Installing into locations other than C:\strawbe (Score:1)

    by Alias (5735) on 2008.01.25 10:43 (#60528) Homepage Journal

    1. Win32 Makefile doesn't enable relocation by default, so it hasn't been tested enough for me.
    
    2. CPAN.pm and another config file have specific paths (I've made a path-agnostic CPAN.pm for the next release as a first stage).
    
    3. I refuse to limit people to only be able to have working Perl applications if they launch a "Perl Console".
    
    Perl apps should Just Work, regardless of how you run them.
    
    If I do Start... Run... perlapplication, and it fails, it's not good enough.
    
    I'm sure there's a better solution that DOES Just Work, but your one isn't good enough I'm afraid.
    

    Reply to This

    Parent

    • Re: (Score:1)

      by Corion (7288)

      The Win32 Makefile does not enable relocation by default because Perl has always been relocatable on Win32. It's only some modules that aren't without some patching. I've used Perl since 5.6 on Windows in various directories and never encountered any problem that wasn't related to badly written Perl modules that couldn't cope with whitespace in directories.

      Double-clicking any Perl program will work even if Perl is not in $ENV{PATH} on Windows, because you (presumably) set up the file association between th