Skip Menu |

This queue is for tickets about the Data-Float CPAN distribution.

Report information
The Basics
Id: 36731
Status: resolved
Priority: 0/
Queue: Data-Float

People
Owner: Nobody in particular
Requestors: ANDK [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.009
Fixed in: (no value)



Subject: create_makefile_pl argument should be 'traditional'
The Module::Build::Compat manpage says about the choice of the style parameter for the create_makefile_pl option: A Makefile.PL will be created in the "traditional" style, i.e. it will use "ExtUtils::MakeMaker" and won’t rely on "Mod‐ ule::Build" at all. In order to create the Makefile.PL, we’ll include the "requires" and "build_requires" dependencies as the "PREREQ_PM" parameter. You don’t want to use this style if during the "perl Build.PL" stage you ask the user questions, or do some auto-sensing about the user’s environment, or if you subclass Module::Build to do some customization, because the vanilla Makefile.PL won’t do any of that. Given that your Build.PL does neither autosensing nor ask the user nor anything like subclassing, it seems clearly the best choice among all options, at leasst as I understand it. 'passthrough' on the other hand stops the user without Module::Build installed or forces him to install it and breaks if it isn't installable for whatever reason. Thanks,
I don't want to support building in the full EU:MM way. The canonical way to build Data::Float is through M:B, but I'm willing to have glue logic to make a blind "perl Makefile.PL; make" work as an interface to the build system. That's what "passthrough" does.