Differences

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

--- en:release:2.86_release_notes [2017/09/27 05:27] – [Source Components and Source Distributions] anupama
+++ en:release:2.86_release_notes [2023/03/13 01:46] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 **Release Name:** 2.86
@@ Line 74: / Line 77: @@
   * If you wish to work with password protected collections, here's [[http://wiki.greenstone.org/doku.php?id=en:release:2.86_release_notes&#problemauthenticated_collections_require_constant_authentication|a workaround]] to the bug of constantly requiring to authenticate yourself.
   * To get your Greenstone installation set up as a remote server so that other GLI clients can connect to it, refer to the section [[2.86_Release_Notes#Working_with_Remote_Greenstone_and_the_GLI-Client | Working with Remote Greenstone and the GLI-Client]].
+==== Running the installer in text-only mode ====
+  - Give the binary of the installer execute permissions
+  - Then run it by passing in the text-only flag.
+  - Follow the instructions on the screen thereafter. If you mistype at any stage, press ctrl-C to start again.
+<code>
+> ./Greenstone-2.86rc2-linux text-only
+----------------------------
+Extracting java installer...
+----------------------------
+Extraction Complete
+You can now run "java -jar greenstone.jar text" to run the installer from the command line
+>
+</code>
@@ Line 93: / 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 108: / Line 128: @@
 ./makejar.sh
 </code>
-**Note** that some Linux and Mac machines may require to you to ''export CFLAGS="-fPIC $CFLAGS"'' before running the ''./makegs2.sh script''. If compilation fails when the ''CFLAGS'' has not been set to include ''-fPIC'', then try
+**Note** that some Linux and Mac machines may require to you to export ''CFLAGS="-fPIC $CFLAGS"'' before running the ''./makegs2.sh'' script. If compilation fails when the ''CFLAGS'' has not been set to include ''-fPIC'', then try
-<pre>export CFLAGS="-fPIC $CFLAGS"
+<pre>
+export CFLAGS="-fPIC $CFLAGS"
 make distclean
-makegs2.sh</pre>
+makegs2.sh gnome-lib
+</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 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 148: / 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 161: / 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 197: / 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>
-==== Running the installer in text-only mode ====
-  - Give the binary of the installer execute permissions
-  - Then run it by passing in the text-only flag.
-  - Follow the instructions on the screen thereafter. If you mistype at any stage, press ctrl-C to start again.
-<code>
-> ./Greenstone-2.86rc2-linux text-only
-----------------------------
-Extracting java installer...
-----------------------------
-Extraction Complete
-You can now run "java -jar greenstone.jar text" to run the installer from the command line
->
-</code>
 ==== Setting the Preview Command in GLI====
@@ Line 1042: / 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.