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.
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: Module::Build::Compat bug :(
Ovid on 2007-08-20T13:15:29
perldoc Module::Build. See MOTIVATIONS.
Re: Module::Build::Compat bug :(
Corion on 2007-08-20T16:35:02
... 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: Module::Build::Compat bug :(
Aristotle on 2007-08-20T16:13:38
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: Module::Build::Compat bug :(
chromatic on 2007-08-20T16:58:00
If you can get all of the nutrition you need from an IV, why bother eating a nice steak dinner?
Moo!
mr_bean on 2007-08-21T01:06:30
What's your beef?
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?
Re:Weird dependencies
Ovid on 2007-08-20T16:19:19
Ah, shoot. That's a nasty habit of mine, just tossing things in there. Another fix to make
:)
