Author: dagolden
Date: Wed Nov 18 22:29:12 2009
New Revision: 13564

Modified:
   Module-Build/trunk/lib/Module/Build/Bundling.pod

Log:
remove use lib from Bundling docs

Modified: Module-Build/trunk/lib/Module/Build/Bundling.pod
==============================================================================
--- Module-Build/trunk/lib/Module/Build/Bundling.pod    (original)
+++ Module-Build/trunk/lib/Module/Build/Bundling.pod    Wed Nov 18 22:29:12 2009
@@ -5,7 +5,6 @@
 =head1 SYNOPSIS
 
   # Build.PL
-  use lib '.';
   use inc::latest 'Module::Build';
 
   Module::Build->new(
@@ -19,7 +18,7 @@
 
 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 
+to do this.  The first way is to include Module::Build in the
 C<configure_requires> metadata field.  This field is supported by
 recent versions L<CPAN> and L<CPANPLUS> and is a standard feature
 in the Perl core as of Perl 5.10.1.  Module::Build now adds itself
@@ -50,7 +49,6 @@
 A "bundling" Build.PL replaces the initial "use" line with a nearly
 transparent replacement:
 
-  use lib '.';
   use inc::latest 'Module::Build';
 
   Module::Build->new(
@@ -58,11 +56,6 @@
     license => 'perl',
   )->create_build_script;
 
-The inital C<lib> line ensures that the top-level distribution directory is
-added to C<@INC> so that C<inc::latest> loads from C<./inc/latest.pm>.  You
-SHOULD NOT add 'inc' to C<@INC> (unless you have other special reasons for
-doing so) -- that's not how C<inc::latest> works.
-
 For I<authors>, when "Build dist" is run, Module::Build will be
 automatically bundled into C<inc> according to the rules for
 L<inc::latest>.
@@ -83,7 +76,7 @@
   use inc::latest 'Devel::AssertOS::Unix';
   use inc::latest 'Module::Build';
 
-  Module::Build->new(  
+  Module::Build->new(
     module_name => 'Foo::Bar',
     license => 'perl',
   )->create_build_script;
@@ -116,7 +109,7 @@
 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.)  
+(A future release of Module::Build will hopefully address this deficiency.)
 
 For example, if you need C<Wibble>, but C<Wibble> depends on C<Wobble>,
 your Build.PL might look like this:
@@ -125,7 +118,7 @@
   use inc::latest 'Wibble';
   use inc::latest 'Module::Build';
 
-  Module::Build->new(  
+  Module::Build->new(
     module_name => 'Foo::Bar',
     license => 'perl',
   )->create_build_script;
@@ -147,7 +140,7 @@
 =head1 SEE ALSO
 
 perl(1), L<inc::latest>, L<Module::Build>(3), L<Module::Build::API>(3),
-L<Module::Build::Cookbook>(3), 
+L<Module::Build::Cookbook>(3),
 
 =cut
 

Reply via email to