en:release:2.86_release_notes
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
en:release:2.86_release_notes [2016/07/12 05:26] – 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 | **Release Name:** 2.86 | ||
Line 74: | Line 77: | ||
* If you wish to work with password protected collections, | * If you wish to work with password protected collections, | ||
* 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# | * 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# | ||
+ | |||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | < | ||
+ | > ./ | ||
+ | ---------------------------- | ||
+ | Extracting java installer... | ||
+ | ---------------------------- | ||
+ | |||
+ | Extraction Complete | ||
+ | You can now run "java -jar greenstone.jar text" to run the installer from the command line | ||
+ | > | ||
+ | </ | ||
Line 93: | Line 113: | ||
* Perl 8 or later. For windows, you can get ActivePerl. | * Perl 8 or later. For windows, you can get ActivePerl. | ||
- | <TABAREA tabs=" | + | |
< | < | ||
- | <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. | - 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: \\ < | - Use a terminal to extract the downloaded file's contents into your Greenstone installation folder: \\ < | ||
Line 107: | Line 127: | ||
./ | ./ | ||
./ | ./ | ||
- | </ | + | </ |
- | </TAB> | + | **Note** that some Linux and Mac machines may require to you to export '' |
+ | < | ||
+ | export CFLAGS=" | ||
+ | make distclean | ||
+ | makegs2.sh gnome-lib | ||
+ | </ | ||
+ | **Note** | ||
< | < | ||
- | <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** | 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** | ||
< | < | ||
Line 142: | 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. | - 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' | - If you want to re-compile GLI go into your Greenstone' | ||
- | </ | + | |
< | < | ||
- | <TAB> | + | <tabbox Source dist Linux/Mac> |
- Download Source Distribution. | - 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:// | - 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:// | ||
Line 155: | Line 181: | ||
</ | </ | ||
- You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation' | - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation' | ||
- | </ | + | |
- | < | + | < |
- | <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** | 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** | ||
< | < | ||
Line 191: | 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: '' | - If you wish to compile up the GLI jar files, such as for Remote Greenstone situations, run the following from within the gli folder: '' | ||
- You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation' | - You will need to enable the Administration pages if you want access to them. Do so by editing your Greenstone installation' | ||
- | </TAB> | + | </tabbox> |
- | </ | + | |
- | ==== 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. | ||
- | |||
- | < | ||
- | > ./ | ||
- | ---------------------------- | ||
- | Extracting java installer... | ||
- | ---------------------------- | ||
- | |||
- | Extraction Complete | ||
- | You can now run "java -jar greenstone.jar text" to run the installer from the command line | ||
- | > | ||
- | </ | ||
==== Setting the Preview Command in GLI==== | ==== Setting the Preview Command in GLI==== | ||
Line 329: | Line 339: | ||
* If you had already built the collection, you can Preview it straight away. Any document page in the collection should provide a link in green at the bottom labelled Add Comment. If you're not already logged in, you will be taken to a log in screen and, once authenticated, | * If you had already built the collection, you can Preview it straight away. Any document page in the collection should provide a link in green at the bottom labelled Add Comment. If you're not already logged in, you will be taken to a log in screen and, once authenticated, | ||
- | Users need to have an account in your digital library in order to add comments. | + | **Notes: |
+ | * User comments cannot be added if the GS2 server is run from GLI. Run the standalone GS2 server to add user comments instead. | ||
+ | * Users need to have an account in your digital library in order to add comments. | ||
+ | - Go to your Greenstone home web page. | ||
+ | - Click on the Administration Page link | ||
+ | - Click the Add a New User link to the left | ||
+ | - You'll be requested for the admin username (type " | ||
+ | - Enter the username and password for the new user. The password has to be between 3 and 8 characters long. | ||
+ | - In the Groups field, type " | ||
+ | - Press the Submit button. | ||
Line 376: | Line 395: | ||
**4. Migrating to 2.86** | **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, | + | To switch to version 2.86 from an earlier Greenstone version with minimal risks, you could i) back up your collections, |
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. | 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 497: | Line 516: | ||
These instructions are more Greenstone 2.86-specific than the [[http:// | These instructions are more Greenstone 2.86-specific than the [[http:// | ||
- | The following are steps to follow if you're on **Windows**. On **Linux**, you can skip steps 1 and 2, otherwise things are similar. For instance, you'll want to launch *.bash or *.sh script equivalents to the batch files listed. Also, you'll want to use forward slashes (/) instead of the Windows' | + | The following are steps to follow if you're on **Windows**. On **Unix based systems**, you can skip steps 1 and 2, otherwise things are similar. For instance, on Unix systems, you'll want to launch *.bash or *.sh script equivalents to the batch files listed. Also, you'll want to use forward slashes (/) instead of the Windows' |
Line 577: | Line 596: | ||
**Useful resources** | **Useful resources** | ||
- | * [[http:// | + | * [[http:// |
Line 1027: | Line 1046: | ||
**Important: | **Important: | ||
+ |
en/release/2.86_release_notes.1468301185.txt.gz · Last modified: 2016/07/12 05:26 (external edit)