NAME<\/a> Module::Build::Bundling \u2212 How to bundle Module::Build with a distribution<\/p>\n # Build.PL WARNING<\/small> — THIS IS AN EXPERIMENTAL FEATURE<\/small><\/b><\/p>\n In order to install a distribution using Module::Build, users must have Module::Build available on their systems. There are two ways to do this. The first way is to include Module::Build in the “configure_requires” metadata field. This field is supported by recent versions CPAN<\/small> and CPANPLUS<\/small> and is a standard feature in the Perl core as of Perl 5.10.1. Module::Build now adds itself to “configure_requires” by default.<\/p>\n The second way supports older Perls that have not upgraded CPAN<\/small> or CPANPLUS<\/small> and involves bundling an entire copy of Module::Build into the distribution\u2019s “inc\/” directory. This is the same approach used by Module::Install, a modern wrapper around ExtUtils::MakeMaker for Makefile.PL based distributions.<\/p>\n The “trick” to making this work for Module::Build is making sure the highest version Module::Build is used, whether this is in “inc\/” or already installed on the user\u2019s system. This ensures that all necessary features are available as well as any new bug fixes. This is done using the experimental inc::latest module, available on CPAN.<\/small><\/p>\n A “normal” Build.PL looks like this (with only the minimum required fields):<\/p>\n use Module::Build; A “bundling” Build.PL replaces the initial “use” line with a nearly transparent replacement:<\/p>\n use inc::latest ‘Module::Build’; For authors<\/i>, when “Build dist” is run, Module::Build will be automatically bundled into “inc” according to the rules for inc::latest.<\/p>\n For users<\/i>, inc::latest will load the latest Module::Build, whether installed or bundled in “inc\/”.<\/p>\n The same approach works for other configuration dependencies — modules that must<\/i> be available for Build.PL to run. All other dependencies can be specified as usual in the Build.PL and CPAN<\/small> or CPANPLUS<\/small> will install them after Build.PL finishes.<\/p>\n For example, to bundle the Devel::AssertOS::Unix module (which ensures a “Unix-like” operating system), one could do this:<\/p>\n use inc::latest ‘Devel::AssertOS::Unix’; The “inc::latest” module creates bundled directories based on the packlist file of an installed distribution. Even though “inc::latest” takes module name arguments, it is better to think of it as bundling and making available entire distributions<\/i>. When a module is loaded through “inc::latest”, it looks in all bundled distributions in “inc\/” for a newer module than can be found in the existing @INC array.<\/p>\n Thus, the module-name provided should usually be the “top-level” module name of a distribution, though this is not strictly required. For example, Module::Build has a number of heuristics to map module names to packlists, allowing users to do things like this:<\/p>\n use inc::latest ‘Devel::AssertOS::Unix’;<\/p>\n even though Devel::AssertOS::Unix is contained within the Devel-CheckOS distribution.<\/p>\n At the current time, packlists are required. Thus, bundling dual-core modules, including Module::Build<\/i>, may require a \u2019forced install\u2019 over versions in the latest version of perl in order to create the necessary packlist for bundling. This limitation will hopefully be addressed in a future version of Module::Build.<\/p>\n WARNING<\/small> — How to Manage Dependency Chains<\/b> For example, if you need “Wibble”, but “Wibble” depends on “Wobble”, your Build.PL might look like this:<\/p>\n use inc::latest ‘Wobble’; Authors are strongly suggested to limit the bundling of additional dependencies if at all possible and to carefully test their distribution tarballs on older versions of Perl before uploading to CPAN.<\/small><\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
BUNDLING OTHER CONFIGURATION DEPENDENCIES<\/a>
AUTHOR<\/a>
SEE ALSO<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
use inc::latest ‘Module::Build’;
Module::Build\u2212>new(
module_name => ‘Foo::Bar’,
license => ‘perl’,
)\u2212>create_build_script;<\/p>\nDESCRIPTION <\/a> <\/h2>\n
Module::Build\u2212>new(
module_name => ‘Foo::Bar’,
license => ‘perl’,
)\u2212>create_build_script;<\/p>\n
Module::Build\u2212>new(
module_name => ‘Foo::Bar’,
license => ‘perl’,
)\u2212>create_build_script;<\/p>\nBUNDLING OTHER CONFIGURATION DEPENDENCIES <\/a> <\/h2>\n
use inc::latest ‘Module::Build’;
Module::Build\u2212>new(
module_name => ‘Foo::Bar’,
license => ‘perl’,
)\u2212>create_build_script;<\/p>\n
Before bundling a distribution you must ensure that all prerequisites are also bundled and load in the correct order. For Module::Build itself, this should not be necessary, but it is necessary for any other distribution. (A future release of Module::Build will hopefully address this deficiency.)<\/p>\n
use inc::latest ‘Wibble’;
use inc::latest ‘Module::Build’;
Module::Build\u2212>new(
module_name => ‘Foo::Bar’,
license => ‘perl’,
)\u2212>create_build_script;<\/p>\nAUTHOR <\/a> <\/h2>\n