SF.net SVN: ledger-smb: [855] branches/1.2/INSTALL

[..hidden..]

Revision: 855
          http://svn.sourceforge.net/ledger-smb/?rev=855&view=rev
Author:   einhverfr
Date:     2007-03-05 22:26:49 -0800 (Mon, 05 Mar 2007)

Log Message:
-----------
reworking INSTALL instructions so that Build test doesn;t generate spurious errors

Modified Paths:
--------------
    branches/1.2/INSTALL

Modified: branches/1.2/INSTALL
===================================================================
--- branches/1.2/INSTALL	2007-03-06 06:23:56 UTC (rev 854)
+++ branches/1.2/INSTALL	2007-03-06 06:26:49 UTC (rev 855)
@@ -14,32 +14,13 @@
 
 1)  Untar in desired location.
 
-2)  Check Dependencies
-
-The Build.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.)
-
-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
-line.  The test suites currently check to make sure all the perl modules load
-and that a number of numeric tests are passed.
-
-Dependencies which are recommended are needed only for specific functionality
-and may not be required in all circumstances.  These include:
-  * Net::TCLink for credit card processing in a POS environment
-  * Parse::RecDescent for the CLI script host
-
-3)  Decide where to put the user/session management tables.  In general, we
+2)  Decide where to put the user/session management tables.  In general, we
 recommend as follows:
   a)  Single dataset installations should use the user tables in the dataset.
   b)  Multicompany installations should use user tables in a separate dataset
       from any accounting data.
 
-4)  Create central database
+3)  Create central database
 
   a) cd to the sql/ directory of the new ledger directory.
   b) run "psql" with appropriate options to connect to your database.
@@ -48,12 +29,31 @@
   Note that the psql connection should use the same username that you intend to
   use for the user authentication connection.
 
-5)  Set the admin password:
+4)  Set the admin password:
   a)  From psql, determine what admin password you wish to use.  Then type:
       "update users_conf set password = md5('my_password');"
       Naturally you would use your password instead of my_password.
 
-6)  Edit the ledger-smb.conf file as appropriate.
 
+5)  Edit the ledger-smb.conf file as appropriate.
 Congratulations, you have manually installed LedgerSMB 1.2.
 
+6)  Check Dependencies
+
+The Build.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.)
+
+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
+line.  The test suites currently check to make sure all the perl modules load
+and that a number of numeric tests are passed.
+
+Dependencies which are recommended are needed only for specific functionality
+and may not be required in all circumstances.  These include:
+  * Net::TCLink for credit card processing in a POS environment
+  * Parse::RecDescent for the CLI script host
+


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.