Bug 6976 Close loophole allowing borrowers extra holds via opac

[koha.git] / INSTALL.ubuntu

diff --git a/INSTALL.ubuntu b/INSTALL.ubuntu
index 815a4e6..050d15d 100644 (file)
--- a/INSTALL.ubuntu
+++ b/INSTALL.ubuntu
@@ -11,7 +11,7 @@ Modified for Ubuntu by: Chris Nighswonger (cnighswonger AT foundations DOT edu)
 Feedback/bug reports: Koha Developer's List:
 http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
 
-This document last modified: 19 May 2010
+This document last modified: 20 March 2010
 
 Installation Instructions
 =============================
@@ -90,9 +90,7 @@ sources
 
 Run the following command:
 
-    $ sudo cpan MARC::Crosswalk::DublinCore GD GD::Barcode::UPCE Email::Date \
-                HTML::Scrubber Algorithm::CheckDigits::M43_001 Biblio::EndnoteStyle \
-                Locale::Currency::Format
+    $ sudo cpan GD GD::Barcode::UPCE Algorithm::CheckDigits::M43_001 CHI CHI::Driver::Memcached
 
 Note: you may need to run CPAN initialization if you've not run cpan
 before:
@@ -283,7 +281,7 @@ To add a user do:
 
 Option 1: run the Zebra processes from the command line:
 
-1.1 Zebra Search Server
+5.1.1 Zebra Search Server
 
 This process send responses to search requests sent by Koha or
 Z39.50/SRU/SRW clients.
@@ -296,7 +294,7 @@ Note: the user you run Zebra as will be the only user with write permission
       on the Zebra index; in development mode, you may wish to use your
       system user.
 
-1.2 Zebra Indexer
+5.1.2 Zebra Indexer
 
 Added/updated/deleted records in Koha MySQL database must be indexed
 into Zebra. A specific script must be launched each time a bibliographic
@@ -310,7 +308,7 @@ Option 2: run the Zebra process as a daemon, and add to startup process:
 Note that references to $SCRIPT_DIR refer to the directory where
 Koha's command-line scripts are installed, e.g., /usr/share/koha/bin.
 
-1.1 Zebra Search Server
+5.2.1 Zebra Search Server
 
     $ sudo ln -s ${SCRIPT_DIR}/koha-zebra-ctl.sh  /etc/init.d/koha-zebra-daemon
     (Note: ${SCRIPT_DIR} is /usr/share/koha/bin/ by default in a standard install)
@@ -319,7 +317,7 @@ Koha's command-line scripts are installed, e.g., /usr/share/koha/bin.
 
     $ sudo ${SCRIPT_DIR}/koha-zebra-ctl.sh start
 
-1.2 Zebra Indexer
+5.2.2 Zebra Indexer
 
 Add an entry in Koha user crontab to scheduled added/updated/deleted records
 indexing by Zebra with this command:
@@ -329,6 +327,8 @@ indexing by Zebra with this command:
 See check misc/cronjobs/crontab.example for usage examples.
 NOTE: This job should be setup under the kohauser (the default is 'koha').
 
+You can also configure zebra-indexing as an background daemon, see http://wiki.koha-community.org/wiki/Background_indexing_with_Zebra
+
 6. Run the Web Installer, populate the database, initial configuration of settings
 
     Point your browser to http://<servername>:8080/
@@ -363,6 +363,8 @@ NOTE: This job should be setup under the kohauser (the default is 'koha').
     and items as you add them. Check misc/cronjobs/crontab.example for usage examples. See 7.0 above.
     NOTE: This job should be setup under the kohauser (the default is 'koha').
 
+    You can also indexing in background, see 5.2.2 above
+
 7.4 To enable public Z39.50/SRU servers, you'll need to edit your koha-conf.xml and
     change the <listen> options to listen on a TCP port; then restart the zebra daemon.
 
@@ -380,7 +382,7 @@ use the following:
  ./koha_perl_deps.pl -u -m # to identify new Perl dependencies
 
 Install any missing modules
-IMPORTANT: Koha 3.4.x uses Template::Toolkit, this must be installed
+IMPORTANT: Koha 3.6.x uses Template::Toolkit, this must be installed
 before the webinstaller can run
 
  sudo apt-get install libtemplate-perl
@@ -390,7 +392,8 @@ before the webinstaller can run
  make test
  sudo make upgrade
 
-Koha 3.4.x no longer stores items in biblio records so as part of the
+Koha 3.4.x or later no longer stores items in biblio records so 
+if you are upgrading from an older version as part of the
 upgrade you will need to do the following two steps, they can take a
 long time (several hours) to complete for large databases