Differences

This shows you the differences between two versions of the page.

--- en:release:2.86_release_notes [2017/09/27 07:34] – anupama
+++ en:release:2.86_release_notes [2025/08/07 23:52] (current) – updated mailing list address kjdon
@@ Line 1: / Line 1: @@
 **Release Name:** 2.86
@@ Line 110: / Line 113: @@
   * Perl 8 or later. For windows, you can get ActivePerl.
-<TABAREA tabs="Source comp Linux/Mac, Source comp Win, Source dist Linux/Mac, Source dist Win">
 <!-----Source comp Linux/Mac----->
-<TAB>
+<tabbox Source comp Linux/Mac>
   - Download the Source Component tar.gz file that matches with your Greenstone binary version, and put it in your Greenstone installation folder.
   - Use a terminal to extract the downloaded file's contents into your Greenstone installation folder: \\ <code>cd <your greenstone folder>
@@ Line 132: / Line 135: @@
 </pre>
 **Note** also that some Linux machines don't need gnome-lib at all, in which case, the first compilation step above would just be ''./makegs2.sh''. To tell whether your Linux machine needs gnome-lib, try compiling it without it first. If compilation fails during wvware, then you need gnome-lib. The Mac Mountain Lion and Leopard machines we tested it on required gnome-lib.\\ Note also that on 64 bit unix systems, ''-fPIC'' is automatically prepended to the ''CFLAGS'' environment variable by the ''./makegs2.sh'' script, as this tends to be needed for compiling.
-</TAB>
 <!-----Source comp Win----->
-<TAB>
+<tabbox Source comp Win>
 It's handy to create a batch script to set the environment. Create a file containing the following, make sure to replace the paths with your own, and save the file as **setupenv.bat**
 <code>@echo off
@@ Line 166: / Line 168: @@
   - It will take some minutes to compile after which, if there are no errors, you can start running GLI or the gs2-server.
   - If you want to re-compile GLI go into your Greenstone's gli subfolder: ''cd gli''. Next, type: ''makegli.bat''. To re-compile the GLI jar files, such as used for Remote Greenstone situations, type: ''makejar.bat''.
-</TAB>
 <!-----Source dist Linux/Mac----->
-<TAB>
+<tabbox Source dist Linux/Mac>
   - Download Source Distribution.
   - If you want to compile up gnome-lib yourself, skip this step. If you want to use a pre-compiled gnome-lib binary (to save on all the time of compiling gnome-lib), download the gnome-lib-minimal package for your OS by visiting http://trac.greenstone.org/browser/gs2-extensions/gnome-lib/trunk \\ Then unzip the downloaded gnome-lib minimal package into your greenstone2-home/ext
@@ Line 179: / Line 181: @@
 </code> \\ **Note** that some Linux machines don't need gnome-lib at all, in which case, the first compilation step above would just be ''./makegs2.sh''. To tell whether your Linux machine needs gnome-lib, try compiling it without it first. If compilation fails during wvware, then you need gnome-lib. The Mac Mountain Lion and Leopard machines we tested it on required gnome-lib.
   - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation's ''etc/main.cfg'' file. Change the ''status'' field value from ''disabled'' to ''enabled''. In that case, you may also want to change the admin password for the Adminstration pages. Use a DOS prompt to run: ''gsicontrol.bat configure-admin'' which will allow you to (re)set the password for username ''admin'' (the default admin password is the same as the username). The password has to be between 3 and 8 characters long.
-</TAB>
-<!-----Source comp Win----->
+<!-----Source dist Win----->
-<TAB>
+<tabbox Source dist Win>
 It's handy to create a batch script to set the environment. Create a file containing the following, make sure to replace the paths with your own, and save the file as **setupenv.bat**
 <code>@echo off
@@ Line 215: / Line 217: @@
   - If you wish to compile up the GLI jar files, such as for Remote Greenstone situations, run the following from within the gli folder: ''makejar.bat''.
   - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation's ''etc/main.cfg'' file. Change the ''status'' field value from ''disabled'' to ''enabled''. In that case, you may also want to change the admin password for the Administration pages. Use a DOS prompt to run: ''gsicontrol.bat configure-admin'' which will allow you to (re)set the password for username ''admin'' (the default admin password is the same as the username). The password has to be between 3 and 8 characters long.
-</TAB>
+</tabbox>
-</TABAREA>
@@ Line 394: / Line 395: @@
 **4. Migrating to 2.86**
-To switch to version 2.86 from an earlier Greenstone version with minimal risks, you could i) back up your collections, ii) install 2.86 in a new home directory (to specified to the installer), and iii) copy the collect sub-directory from the old to the new version. If you are presently using a recent previous version of Greenstone (2.8x), the collections should be immediately available for use; if not, particularly for collections built under older versions of Greenstone, it should suffice to rebuild the collections under the new version. Any problems can be addressed to this list or the main Greenstone users list (http://list.waikato.ac.nz/mailman/listinfo/greenstone-users).
+To switch to version 2.86 from an earlier Greenstone version with minimal risks, you could i) back up your collections, ii) install 2.86 in a new home directory (to specified to the installer), and iii) copy the collect sub-directory from the old to the new version. If you are presently using a recent previous version of Greenstone (2.8x), the collections should be immediately available for use; if not, particularly for collections built under older versions of Greenstone, it should suffice to rebuild the collections under the new version. Any problems can be addressed to the greenstone mailing list [[greenstone-users@lists.sourceforge.net]].
 If you want to transfer information on users and user groups, the corresponding databases (users.gdb, key.gdb) should be copied from the etc sub-directory in the old collection to the new one. Of course if you have customised your previous version (main.cfg, style.css, macros, etc.), the old versions should also be copied to the new installation. When all is working perfectly, the old installation can be deleted.
@@ Line 1045: / Line 1046: @@
 **Important:** If you are one of our valued translators and have contributed again since the 2.85 release, and we missed adding your name here due to unfortunate oversight, then your name belongs in the above list. Therefore please contact us and we'll be thrilled to add you in here.