Actually committing the switch away from Moduel::Build

git-svn-id: https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/trunk@1645 4979c152-3d1c-0410-bac9-87ea11338e46

1 files changed, 6 insertions, 6 deletions

diff --git a/INSTALL b/INSTALL
index 3fcb1013..2da48d16 100644
--- a/INSTALL
+++ b/INSTALL
@@ -16,15 +16,15 @@ MANUAL INSTALL:
 
 2)  Check Dependencies
 
-The Build.PL script can be used to test for unmet dependencies and run other
+The Makefile.PL script can be used to test for unmet dependencies and run other
 tests.  It doesn't install anything yet, but it will tell you what you are 
-missing.  To check for dependencies, run "perl Build.PL" from the command line.
-Missing dependencies can generally be installed via a Linux distributor's
-package manager or by CPAN. (Build.PL itself uses Module::Build, which is
-available in packages like perl-Module-Build or libmodule-build-perl.)
+missing.  To check for dependencies, run "perl Makefile.PL" from the command
+line.  Missing dependencies can generally be installed via a Linux distributor's
+package manager or by CPAN. (Makefile.PL itself uses Module::Install, which is
+available in packages like perl-Module-Install or libmodule-install-perl.)
 
 Once this is done and dependencies are satisfied, you can check to see whether
-the installation nominally works by running "./Build test" from the command
+the installation nominally works by running "make test" from the command
 line.  The test suites currently check to make sure all the perl modules load
 and that a number of numeric tests are passed.