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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'm not a big fan of MI, and I think the main reason is it's too freaking magical. This "feature" is a perfect example of magic gone bad. It adds a _tiny_ bit of convenience (arguably less than tiny) while adding significant headaches for those who don't understand WTF is going on.

    • I agree in full. It's like, "Here, let's declare our deps in this file, except for the secret ones that we assume!"
      --
      --fREW
      http://blog.afoolishmanifesto.com
  • I personally have been annoyed when I go to work on a project and when I try to run the Makefile.PL for the purposed of getting dependencies installed (either via "make installdeps" or cpanm --installdeps .) I get a list of 'pre dependencies', mostly stuff to get Module::Install bootstrapped. I know there's 'config_requires' but this doesn't seem to help with the problem. Typically I solve it with a hack, when I create a new local::lib for a project I preload most of the common Module::Install plugins I u
    --
    Waiting on the Road to Eventually, I lost my Place On Line
  • If only because it would make stuff like this [github.com] unnecessary.
  • I really dislike this particular MI magic. Even for experts it can be a pain to guess what the right Module::Install plugin to install.
  • Yes, agreed...

    And a command-line option that lists the plugins for installing via cpanm would be great, too!

    --
    The new Strawberry Perl for Windows has been released! Check http://strawberryperl.com for it.