The Perl Toolchain Summit needs more sponsors. If your company depends on Perl, please support this very important event.

Changes for version 0.27_02

  • Provided initial support for the --prefix installation parameter, which acts like MakeMaker's PREFIX. It is still highly recommended NOT to use it when you could reasonably use --install_base or --install_path or --install_dest, but that's just because the way --prefix is designed is weird and unpredictable. Ultimately the choice rests with the installing user. [Patches by Michael Schwern and Rob Kinyon]
  • Fixed a bug in subclass() which prevented people from using it to subclass subclasses of Module::Build. [Chris Dolan]
  • Added a 'pure_install' action, which for the time being is identical to the 'install' action. [Jos Boumans]
  • Fixed a POD error in an L<http://...> tag. [Offer Kaye]
  • Note several options for automatically creating a new module dev tree. [Suggested by Eric Wilhelm]
  • Removed some hard-coded references to File::Spec::Unix in the creation of HTML docs, which should help that code work in more places, and help people not to panic when they look at it. [Spotted by Yves]
  • We now use Pod::Readme by default (instead of Pod::Text) to generate the README file when the 'create_readme' option is used. If Pod::Readme is not installed, we will still fall back to using Pod::Text. [Robert Rothenberg]
  • The values of the "prefix", "install_base", "install_path", and "install_dest" parameters can now begin with "~" or "~user", and we'll de-tilde-ify them by using glob().
  • The (optional) auto-creation of the README and Makefile.PL files have been moved from the 'distdir' action to the 'distmeta' action. [David Golden]
  • When looking for a .modulebuildrc file, we now use a fancier method of trying to find the home directory, because $ENV{HOME} isn't a very cross-platform variable. [Robert Rothenberg]
  • We now memoize the output of the internal _default_INC() method, since it uses backticks and might be kind of slow.
  • When processing XS files, we now look for a typemap in lib/ as well as using the system's default typemap. [John Peacock]
  • The DESTDIR, PREFIX, and INSTALL_BASE arguments to "make install" are now supported for pass-through Makefiles (they've been supported for quite a while as arguments to "perl Makefile.PL"). [Requested by Guillaume Rousse]
  • Test::Harness has changed its output format in recent versions, which threw off one of our tests. We now allow for this different format. [Reported by Scott Godin]
  • Fixed an issue that prevented Module::Build from upgrading itself using its own API (which is how CPANPLUS uses it). There are still some issues with this solution, however. See ticket #13169 in rt.cpan.org. [Reported by Jos Boumans]
  • Fixed a fatal error that occurred when a distribution's author could not be determined from its POD nor from the call to Module::Build->new() in its Build.PL. See ticket #12318 in rt.cpan.org. [Reported by Jos Boumans]
  • Apparently on Windows and cygwin it's not possible to use the "-pi" switch to perl without a backup extension, so now we use ".bak" and remove the backup file when we're done. Thus the "dist" action for Module::Build itself can now be run on those platforms. [Yitzchak Scott-Thoennes]
  • Improved the handling of auto_features in the config_data access script. [Yitzchak Scott-Thoennes]

Changes for version 0.27_01

  • Backward-incompatible (but better) changes:
  • When using the 'install_base' option to choose a directory for installing everything, perl modules now go into lib/perl5/ instead of just lib/. It seems this is more consistent with people's expectations, and the way I had it before was a bit peculiar to the way I like things in my own home directory. [Michael Schwern]
  • When the user is using the 'install_base' option, scripts will now be installed by default in $install_base/bin/ rather than $install_base/script/ . [Jan Hudec and Michael Schwern]
  • Major changes:
  • The auto_features mechanism will now re-evaluate dependencies every time feature() is called for an auto-feature, rather than freezing the success/failure value during 'perl Build.PL' and using that value for all eternity (or module update, whichever comes first). This applies to both $build->feature() and FooModule::ConfigData->feature() calls. [Requested by many]
  • Added the meta_add and meta_merge mechanisms, which let the module author add/merge arbitrary entries into the META.yml file.
  • Now reads per-action default options from '$ENV{HOME}/.modulebuildrc' if it exists. Command line options override anything set in the rc file.
  • Extend prerequisite specifications to apply to all actions. It is now a fatal error if 'requires' or 'conflicts' for a given action are not satisfied, except where necessary for backwards compatability. Also, added '--force' options to ignore the fatal errors. (NOTE: this is a somewhat experimental feature, we may morph this around a bit before final release!)
  • The creation of Unix man pages is no longer a strict necessity - it has now been turned into an 'auto-feature' contingent on the presence of Pod::Man and a location specified for man pages to go.
  • A user-specified 'install_path' setting will now take precedence over an 'install_base' setting. This allows the user to use 'install_base' to set the base for all elements in one go, and then use 'install_path' to override specific paths or add paths for additional kinds of targets.
  • Split the main documentation from 'Module/Build.pm' into two sections. The user level documentation and overview remains in 'Module/Build.pm', while a new document, 'Module/Build/Authoring.pod', has been created for module authors.
  • Minor changes:
  • new_from_context() was losing its arguments in some cases (and not because of inadequate training in forensic debate) - we now pass its arguments directly to the Build.PL script rather than merging them in afterwards.
  • Let resume() return an object blessed into the appropriate class if the user has provided a subclass, as specified by the 'build_class' property. This allows current() and new_from_context() to behave more like factory methods returning objects of the correct class based on context. [Ray Zimmerman]
  • Refactored methods relating to parsing perl module files for package, version, and pod data into a new class: Module::Build::ModuleInfo. It should not be considered part of Module::Build's API, because we may split it out entirely as a separate CPAN module that we depend on.
  • Added new method Module::Build::prepare_metadata() for authors to override in order to add custom fields to META.yml.
  • We now use Test::More for our regression tests. If the user doesn't have it installed, we include a copy in t/lib/ that we can use during testing.
  • When copying files in the 'distdir' action, set permissions to match the original files. [Julian Mehnle]
  • When adding files like META.yml to the MANIFEST, we now tell the user we're doing so by printing one of the "Added to MANIFEST: ..." lines. [Ron Savage]
  • Added a runtime_params() method, which lets a module author see which parameters were overridden by the user on the command line (or in whatever paradigm the user originally invoked Module::Build from). [David Wheeler]
  • Added the current_action() method, which, surprisingly, returns the name of the currently running action. [David Wheeler]
  • Added docs for run_perl_script().
  • Added some stuff to the docs about why PREFIX is unsupported, and what to use instead. [Steve Purkis]
  • The simple get/set accessor methods for all the 'parameters' like verbose(), license(), etc. now have auto-generated documentation in Module/Build.pm.
  • Created a Cookbook entry for 'Adding new elements to the install process'
  • We now add META.yml to the MANIFEST when META.yml is created, not when MANIFEST is created. [Spotted by Ron Savage]
  • Added some additional patterns to the suggested MANIFEST.SKIP contents, and changed the docs so that we encourage the user to use the MANIFEST.SKIP. [Ron Savage]
  • Eliminated a redundant recipe from the Cookbook, now that there are some more extensive recipes on how to add stuff to the build/install sequences.
  • Eliminated an undefined-variable warning when testing under perl 5.005
  • When building HTML documentation, 'html_backlink' and 'html_css' properties are now first-class properties, so they can be set from the command line. [Suggested by Sagar R. Shah]
  • Have script_files default to everything in bin. I believe this is the least surprising behavior. [Suggested by Michael Schwern]
  • If script_files is given a directory, consider each file in that directory tree as a script to be installed. This avoids having to remember to add to the script_files list every time you add a program. [Suggested by Michael Schwern]
  • We now only load Pod::Man when we actually need to build man pages.
  • We now make Test::Harness use our carefully-selected path to a perl executable regardless of Test::Harness's version. Previously we let it figure stuff out for itself if it was a reasonably modern version, but it's safer to make sure we're using the same perl everywhere.

Documentation

Authoring Module::Build modules
Query or change configuration of Perl modules

Modules

Build and install Perl modules
Default methods for Module::Build
Compatibility with ExtUtils::MakeMaker
Examples of Module::Build Usage
Gather package and POD information from a perl module files
Perl Package Manager file creation
Builder class for Amiga platforms
Stub class for unknown platforms
Builder class for EBCDIC platforms
Builder class for MPEiX platforms
Builder class for MacOS platforms
Builder class for RiscOS platforms
Builder class for Unix platforms
Builder class for VMS platforms
Builder class for VOS platforms
Builder class for Windows platforms
Builder class for AIX platform
Builder class for Cygwin platform
Builder class for Mac OS X platform
Builder class for OS/2 platform

Provides

in lib/Module/Build/Notes.pm
in lib/Module/Build/PodParser.pm
in lib/Module/Build/Base.pm