Differences

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

--- en:release:3.11_release_notes [2024/09/15 22:52] – [Greenstone 3.11 Release notes] kjdon
+++ en:release:3.11_release_notes [2025/07/14 21:18] (current) – [Adding source code to a binary release] kjdon
@@ Line 33: / Line 33: @@
 ==== Installing and running the binary release====
-  * Download the appropriate binary release for your operating system and run it.
+  * [[https://www.greenstone.org/download | Download]] the appropriate binary release for your operating system and run it.
 === Mac OS Notes ===
@@ Line 47: / Line 47: @@
 === Linux Notes ===
-  * You will need to set the file to be executable before running it. e.g. \\ In a terminal ''chmod a+x Greenstone-3.11-linux''\\ or on Ubuntu, you can right-click on the installer, choose Properties, Go to the Permissions tab and ensure the "Execute: Allow executing file as program" tickbox is ticked.
+  * You will need to set the file to be executable before running it. e.g. \\ In a terminal ''chmod a+x Greenstone-3.11-linux-x64''\\ or on Ubuntu, you can right-click on the installer, choose Properties, Go to the Permissions tab and ensure the "Execute: Allow executing file as program" tickbox is ticked.
     * The installer initially unpacks into a temporary directory (/tmp on linux). If you wish to change this, set the TMPDIR environment variable.
 Note that in some cases, the following **doesn't** work
 <code> export TMPDIR=/something/else
- ./Greenstone-3.11-linux</code>
+ ./Greenstone-3.11-linux-x64</code>
 Use the following instead
-<code> TMPDIR=/something/else ./Greenstone-3.11-linux</code>
+<code> TMPDIR=/something/else ./Greenstone-3.11-linux-x64</code>
 ===Windows Notes ===
@@ Line 79: / Line 79: @@
 > ./Greenstone-3.11-linux-x64 -textonly
 </code>
+==== Adding source code to a binary release ====
+  * [[http://wiki.greenstone.org/doku.php?id=en:user_advanced:installation_311#source_component|Windows: Source Component instructions]]
+  * [[http://wiki.greenstone.org/doku.php?id=en:user_advanced:installation_311#source_component1|Linux/Mac: Source Component instructions]]
+==== Installing a source release ====
+  * [[http://wiki.greenstone.org/doku.php?id=en:user_advanced:installation_311#source_distribution|Windows: Source Distribution instructions]]
+  * [[http://wiki.greenstone.org/doku.php?id=en:user_advanced:installation_311#source_distribution1|Linux/Mac: Source Distribution instructions]]
-==== Running Greenstone ====
+===== Running Greenstone =====
 Once you have successfully installed Greenstone3, you can start up the server by choosing Grenstone3 Digital Library from the Start menu (Windows) or running gs3-server.sh/bat. This launches a small server program which starts up Tomcat and launches a browser. A small window pops up which allows you to change some settings for your library and restart the Tomcat server. Closing this program will stop Tomcat running. By default, your library will be available at localhost:8383/greenstone3/library. File->Settings in the Greenstone Server window gives you options to change the port number and which browser it uses by default.
 More notes about running Greenstone can be found in the README.txt file in the top level Greenstone folder.
-=== On a Mac ===
+==== On a Mac ====
 You can either
@@ Line 93: / Line 102: @@
     - gli - starts the librarian interface, which you can use to build/edit collections.
     - gems - used for editing metadata sets.
-==== Building Collections ====
+==== Building Collections =====
 To build collections, run GLI from the Start menu (Windows) or by running gli/gli.sh (gli/gli.bat on windows) in a terminal cd'd to the top level Greenstone3 folder. Tutorial exercises about building collections in Greenstone 3 can be found [[en:tutorials | here]]. Make sure you select the Greenstone3 tab at the top if it is not already selected.
-==== Installing in text-only mode ====
-* Refer to [[http://wiki.greenstone.org/doku.php?id=old:user_advanced:installation#running_the_installer_in_text-only_mode|Running the installer in text-only mode]]
-==== Adding source code to a binary release ====
-  * [[http://wiki.greenstone.org/doku.php?id=old:user_advanced:installation#source_component|Windows: Source Component instructions]]
-  * [[http://wiki.greenstone.org/doku.php?id=old:user_advanced:installation#source_component1|Linux/Mac: Source Component instructions]]
-==== Installing a source release ====
-  * [[http://wiki.greenstone.org/doku.php?id=old:user_advanced:installation#source_distribution|Windows: Source Distribution instructions]]
-  * [[http://wiki.greenstone.org/doku.php?id=old:user_advanced:installation#source_distribution1|Linux/Mac: Source Distribution instructions]]
@@ Line 198: / Line 197: @@
 ==== Useful information ====
-  * To convert a collection's ''collect.cfg'' file to its GS3 equivalent, see [[en:user:gs2_to_gs3#using_a_remote_greenstone_server|here]] for details.
+  * To convert a collection's ''collect.cfg'' file to its GS3 equivalent, see [[en:user:gs2_to_gs3|here]] for details.
   * When you've built a collection of documents, you may discover that there appears to be a copy of all these documents in the collection's //import//, //archives// and //index// subfolders and wonder whether Greenstone could really be so inefficient with disk space as to keep 3 copies of everything. As it happens though, Greenstone uses **hard-links** both on Linux and **Windows**, in order to keep just one set of your documents. Then it simply hardlinks to these, instead of making copies. By default, Windows doesn't show you when files on your filesystem are hard-linked. If you choose to install the Windows extension application [[http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html|Link Shell Extension (LSE)]], it will put red arrows on files that are hard linked.