Author: schwern
Date: Sun Sep 28 13:45:46 2008
New Revision: 11897
Modified:
Module-Build/trunk/ (props changed)
Module-Build/trunk/Changes
Module-Build/trunk/lib/Module/Build/Cookbook.pm
Log:
[EMAIL PROTECTED]: schwern | 2008-09-28 16:42:49 -0400
Added a recipe for bundling Module::Build to the Cookbook.
Modified: Module-Build/trunk/Changes
==============================================================================
--- Module-Build/trunk/Changes (original)
+++ Module-Build/trunk/Changes Sun Sep 28 13:45:46 2008
@@ -2,7 +2,8 @@
0.30_01
New Docs
- - Added a recipe for writing a new action to Module::Build::Cookbook
+ - Added a recipe for writing a new action to the Cookbook
+ - Added a recipe for bundling Module::Build to the Cookbook.
Bug Fixes
- Workaround HARNESS_TIMER env issue in t/compat.t (RT#39635)
Modified: Module-Build/trunk/lib/Module/Build/Cookbook.pm
==============================================================================
--- Module-Build/trunk/lib/Module/Build/Cookbook.pm (original)
+++ Module-Build/trunk/lib/Module/Build/Cookbook.pm Sun Sep 28 13:45:46 2008
@@ -438,7 +438,7 @@
must have been run before your action.
For example, let's say you wanted to be able to write C<./Build
-commit> to test your code and commit it to version control.
+commit> to test your code and commit it to Subversion.
# Build.PL
use Module::Build;
@@ -455,6 +455,50 @@
SUBCLASS
+=head2 Bundling Module::Build
+
+Let's say you want to make sure your distribution has the right
+version of Module::Build. First thing you should do is to set
+C<configure_requires> to your minimum version of Module::Build. See
+L<Module::Build::Authoring>.
+
+But not every build system honors C<configure_requires> yet. Here's
+how you can ship a safe copy of Module::Build, but still use a newer
+installed version to take advantage of bug fixes and upgrades.
+
+First, install Module::Build into F<Your-Project/inc/Module-Build>.
+CPAN will not index anything in the F<inc> directory so this copy will
+not show up in CPAN searches.
+
+ cd Module-Build
+ perl Build.PL --install_base /path/to/Your-Project/inc/Module-Build
+ ./Build test
+ ./Build install
+
+You should now have all the Module::Build .pm files in
+F<Your-Project/inc/Module-Build/lib/perl5>.
+
+Next, add this to the top of your F<Build.PL>.
+
+ my $Bundled_MB = 0.30; # or whatever version it was.
+
+ # Find out what version of Module::Build is installed or fail quietly.
+ # This should be cross-platform.
+ my $Installed_MB =
+ `$^X -le "eval q{require Module::Build; print Module::Build->VERSION}
or exit 1";
+ chomp $Installed_MB;
+ $Installed_MB = 0 if $?;
+
+ # Use our bundled copy of Module::Build if it's newer than the installed.
+ unshift @INC, "inc/Module-Build/lib/perl5" if $Bundled_MB > $Installed_MB;
+
+ require Module::Build;
+
+And write the rest of your F<Build.PL> normally. Module::Build will
+remember your change to C<@INC> and use it when you run F<./Build>.
+
+
+
=head1 AUTHOR
Ken Williams <[EMAIL PROTECTED]>
