Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
Of course, my very first test report for App::Pgrep was a failure. Seems Module::Build::Compat translated a relative path name to an absolute pathname from my system. Damn.
In other news, Miyagawa points out that the name "pgrep" is already taken. Double damn. Suggestions? I was thinking grepp, but I don't like that.
Re: Module::Build::Compat bug :( (Score:1)
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?
Re: (Score:2)
perldoc Module::Build. See MOTIVATIONS [cpan.org].
Re: (Score:1)
... 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.
Re: (Score:1)
EU::MM cannot tell
build_requiresfromrequiresso even very simpleBuild.PLs are often more expressive than their equivalentMakefile.PLs and cannot be translated losslessly.Also, Module::Build makes it easy to autogenerate
Makefile.PL. ExtUtils::MakeMaker cannot autogenerateBuild.PL. Starting from a blank slate, which of the two makes better sense to pick?Re: (Score:1)
If you can get all of the nutrition you need from an IV, why bother eating a nice steak dinner?
Moo! (Score:1)
alternate name (Score:1)
rjbs
Weird dependencies (Score:1)
Say, why does your
Build.PLlist these?Doesn’t it need File::Next or PPI to run, only for installation?
Re: (Score:2)
Ah, shoot. That's a nasty habit of mine, just tossing things in there. Another fix to make :)