Author: kwilliams Date: Tue Jul 15 20:04:36 2008 New Revision: 11538 Modified: Module-Build/trunk/Changes Module-Build/trunk/lib/Module/Build/API.pod
Log: Fix script_files docs Modified: Module-Build/trunk/Changes ============================================================================== --- Module-Build/trunk/Changes (original) +++ Module-Build/trunk/Changes Tue Jul 15 20:04:36 2008 @@ -1,5 +1,9 @@ Revision history for Perl extension Module::Build. + - Fixed the documentation for script_files to indicate that we search + bin/ for scripts by default. It has been this way for several + years. [Spotted by Ron Savage] + 0.2808_02 - Wed Jul 9 16:45:08 PDT 2008 - Experimental support for TAP::Harness with --use-tap-harness option Modified: Module-Build/trunk/lib/Module/Build/API.pod ============================================================================== --- Module-Build/trunk/lib/Module/Build/API.pod (original) +++ Module-Build/trunk/lib/Module/Build/API.pod Tue Jul 15 20:04:36 2008 @@ -683,13 +683,13 @@ An optional parameter specifying a set of files that should be installed as executable Perl scripts when the module is installed. -May be given as an array reference of the files, or as a hash -reference whose keys are the files (and whose values will currently be -ignored). +May be given as an array reference of the files, as a hash reference +whose keys are the files (and whose values will currently be ignored), +as a string giving the name of a directory in which to find scripts, +or as a string giving the name of a single script file. -The default is to install no script files - in other words, there is -no default location where Module::Build will look for script files to -install. +The default is to install any scripts found in a F<bin> directory at +the top level of the distribution. For backward compatibility, you may use the parameter C<scripts> instead of C<script_files>. Please consider this usage deprecated,
