Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Strawberry Perl and the nightmare of installing Padre 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • So firstly, no guarentees if you have more than one Perl installed... no Perls really live together well.

    Secondly, there's known issues in CPAN.pm.

    I recommend uninstalling the July strawberry and trying again with the new October release.

    http://strawberry-perl.googlecode.com/files/strawberry-perl-5.10.1.0.msi [googlecode.com]

    This has a new (dev) CPAN release that might fix your problem, and some updated Perl modules and C libraries that should (hopefully) make the installation much easier.

    Finally, yes, newbies are not REALL

    • I submit that almost anyone installing strawberry already has a perl, and likely more than 1.

      When I install strawberry, I have activestate, cygwin, and I tried building my own. And after that, I have an old strawberry in front of the new strawberry.

      A prominent set of warnings seems appropriate.

      • The way I solved that is as follows:

        I removed the Strawberry specific paths from the PATH environment variable. I then added an icon in the start menu to launch a console shell (cmd.exe), after prepending these paths to PATH first.

        One easy way to do that, is by making a BAT file with the following contents:

        @echo off
        path C:\strawberry\c\bin;C:\strawberry\perl\bin;%path%
        cmd

        But an IMHO nicer alternative is to just create a shortcut with this as the target:

        cmd.exe /k PATH=C:\strawberry\c\bin;C:\strawberry\pe

        • Thanks much! I think I understand, and I will try that.

          In a previous version of strawberry (last one?), when padre tried to update, for me things choked due to failures in the toolchain of padre. Does this likely have to do with the path during the update of padre? (I think that happened before I have the opportunity to intervene...)

          It would be lovely for such advice as yours to be obvious to strawberry perl installers who encounter such problems.

          Thanks again! I love perl, though it can be trying at times.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.