osrf_ctl.sh -l -a stop_all
wget http://evergreen-ils.org/downloads/Evergreen-ILS-2.1.0a.tar.gz tar xzf Evergreen-ILS-2.1.0a.tar.gz
debian-sqeeze
for Debian Squeezeubuntu-lucid
for Ubuntu Lucid Lynx (10.04)cd /home/opensrf/Evergreen-ILS-2.1.0a make -f Open-ILS/src/extras/Makefile.install <distribution>
cd /home/opensrf/Evergreen-ILS-2.1.0a ./configure --prefix=/openils --sysconfdir=/openils/conf make
make STAFF_CLIENT_BUILD_ID=rel_2_1_0 install
sudo chown -R opensrf:opensrf /openils
cd /home/opensrf/Evergreen-ILS-2.1.0a # and offline-config.pl for the offline staff client data uploader perl Open-ILS/src/support-scripts/eg_db_config.pl \ --create-offline --user evergreen --password evergreen \ --hostname localhost --port 5432 --database evergreen
cd /openils/var/web/xul/ rm server ln -s rel_2_1_0/server server
# blow away the default PostgreSQL 9.0 main cluster pg_dropcluster 9.0 main # upgrade your production PostgreSQL 8.4 main cluster pg_upgradecluster --stop 8.4 main # OPTIONAL: blow away your old PostgreSQL 8.4 main cluster # If you don't do this, then you might need to update # opensrf.xml with new port numbers (probably 5433) pg_dropcluster 8.4 main
hstore
PostgreSQL contrib module to your Evergreen database:psql -U evergreen -h localhost -f /usr/share/postgresql/9.0/contrib/hstore.sql -d evergreen
cd /home/opensrf/Evergreen-ILS-2.1.0a psql -U evergreen -h localhost -f Open-ILS/src/sql/Pg/2.0-2.1-upgrade-db.sql evergreen
opensrf.xml
file as the opensrf user:# If you are happy with the default settings in opensrf.xml.example, then: cp -b /openils/conf/opensrf.xml.example /openils/conf/opensrf.xml perl Open-ILS/src/support-scripts/eg_db_config.pl --update-config --service all \ --database evergreen --host localhost --user evergreen --password evergreen # Otherwise, compare /openils/conf/opensrf.xml with /openils/conf/opensrf.xml and # manually copy the new pieces into place in your existing opensrf.xml file
mv /openils/lib/perl5 /openils/lib/perl5-2.0
osrf_ctl.sh -l -a start_all
autogen.sh
NOTE: Troubleshooting: If you run into errors, see: Troubleshooting: Checking for Errors for help finding errors in the log files. You may also ask the evergreen community using the mailing lists. Including error information from the logs will be extremely helpful when seeking assistance.