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.
  • This is something I never got - if your Build.PL can be converted automatically to a Makefile.PL, and thus, obviously doesn't need any of the features that Module::Build offers over ExtUtils::MakeMaker, why would you use Module::Build at all?

    • perldoc Module::Build. See MOTIVATIONS [cpan.org].

      • ... but these are the reasons why Ken Williams wrote Module::Build, not why somebody would use it, just to (down-)convert the file to a Makefile.PL immediately.

    • EU::MM cannot tell build_requires from requires so even very simple Build.PLs are often more expressive than their equivalent Makefile.PLs and cannot be translated losslessly.

      Also, Module::Build makes it easy to autogenerate Makefile.PL. ExtUtils::MakeMaker cannot autogenerate Build.PL. Starting from a blank slate, which of the two makes better sense to pick?

    • If you can get all of the nutrition you need from an IV, why bother eating a nice steak dinner?

  • grepl - grep + pl
    --
    rjbs
  • Say, why does your Build.PL list these?

        build_requires    => {
            'Scalar::Util' => 1.19,
            'Test::More'   => 0,
            'File::Next'   => 0.40,
            'PPI'          => 1.118,
        },

    Doesn’t it need File::Next or PPI to run, only for installation?

    • Ah, shoot. That's a nasty habit of mine, just tossing things in there. Another fix to make :)