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.

The pain of updating Perl 4 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Yes, I know, it's a pain.
    I'm trying to work on that.
    Do you use Vista on your laptop?

    Can you give me some more information about what fails, error messages, and such?
    Do you think it depends on PPM/Activestate packaging? What compiler do you use?

    Sorry, many questions... :-)

    • I don't know exactly what failed, all I know is I had to reinstall Win32::API. I used PPM both times.

      I did have an additional problem when installing CAM::PDF [cpan.org], also with PPM. My virus scanner (Grisoft's AVG) didn't like the double extension of one of the scripts, ".pdf.bat", it block access to that file and it even when I clicked "it's OK to run this file", which interrupted installation of that module. Time and time again. Plus, it apparently broke off installation of the rest of the modules in the to do l
  • Do this or its equivalent.

    perldoc -t perllocal \
      | perl -lne 'print $1 if /"Module" (\S+)/'
      | xargs -n 1 cpan
    • Good idea, except for one detail: the module list is not the list from this installation of perl, but of the previous one, that has already been deleted. So it needs to be a multi-step process:
      1. save the module list to a file
      2. reinstall perl
      3. run the rest of your oneliner using that file as its input
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.