Differences

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

--- en:user_advanced:installation_311 [2025/07/14 21:24] – [Uptodate source code from SVN] kjdon
+++ en:user_advanced:installation_311 [2025/07/15 00:08] (current) – kjdon
@@ Line 1: / Line 1: @@
+====== Advanced Installation: 3.11 ======
+//Updated on 30 Sep 2021, with changes that do not apply for Greenstone 3.10 and earlier.//
-====== Advanced Installation: 3.11 ======
+[[en:user_advanced:installation|Advanced Installation Index Page]] - from here you can access different versions of this page.
-//Updated on 30 Sep 2021, with changes that do not apply for Greenstone 3.10 and earlier.
-For instructions related to compiling GS3.10 from source distribution or with source component, or with source code from before September 2021, refer to the now [[old:user_advanced:installation|older version of this Advanced Installation page]].//
 For most users, the main Greenstone download (also called the "binary") with default settings is sufficient, and is very [[en:beginner:install_basic|easy to install]]. However, there are some instances where you may want or need to go through a more advanced installation process:
@@ Line 424: / Line 424: @@
 -->
-===== Source Code Stability =====
-Note: This page is aimed at Greenstone developers.
-The source code stability system attempts to provide developers with a constant stable code base for development even as the main trunk passes between stable and unstable states. If you are doing development on a working copy of the trunk, but the trunk has bugs which prevent it compiling or running, then it can be very hard to test your changes. Rather than spend time inquiring into those bugs, the stability system gives you a way to temporarily roll your working copy back to the last stable state. Once you have finished testing your changes, you can then roll you working copy forward again and commit your changes. Except in the case where other developers have made significant changes to the trunk, your changes will start working once the trunk is stable again.
-The stability system works by periodically checking out the trunk and testing it for stability, then creating a 'stable' tag if and only if the trunk passes these stability tests. For now the stability tests are as simple as checking that the release kits on all three main operating systems were able to successfully create a release from the trunk. In the future, these checks could be extended to include regression tests, installer tests, tests to the runtime system and anything else which might further 'prove' the stability of the trunk. Stable tags related to Greenstone2 are named 'stable' and stable tags related to Greenstone3 are named 'stable3'.
-To make your working copy stable, change to the root directory of the working copy and run one of these commands:
-<code>
- (For Greenstone2): svn switch http://svn.greenstone.org/gsdl/stable
- (For Greenstone3): svn switch http://svn.greenstone.org/greenstone3/stable3
-</code>
-Or to checkout a fresh stable working copy, run one of these commands:
-<code>
- (For Greenstone2): svn checkout http://svn.greenstone.org/gsdl/stable gsdl
- (For Greenstone3): svn checkout http://svn.greenstone.org/greenstone3/stable3 greenstone3
-</code>
-Then test your changes and/or keep working on them. Once you are ready to commit your changes, switch back to the trunk:
-<code>
- (For Greenstone2): svn switch http://svn.greenstone.org/gsdl/trunk
- (For Greenstone3): svn switch http://svn.greenstone.org/greenstone3/trunk
-</code>
-And commit as normal.
-**Note**: The stable tags are read-only. (Only the nightly tasks that create the stable tags can write to them.) This is for good reason; allowing commits to the stable tag would be lost the next time the trunk was tagged as stable.
-The projects 'gli', 'gs2build', 'indexers' and 'documentation' also have stable tags.
-You can execute a command like the following to switch to the stable tag for one of
-these projects:
-''svn switch <nowiki>http://</nowiki>svn.greenstone.org/**//project-name//**/stable[3]''
-And switch back with:
-''svn switch <nowiki>http://</nowiki>svn.greenstone.org/**//project-name//**/trunk''
-**Note**: Though the stable branches are in separate locations in the repository, they should be considered as one unit. To get a //bona fide// stable working copy, each project which made up the working copy would have to be switched to the stable tag of the project. Mixing of 'stable' and 'stable3' tags would also prevent a working copy from being a //bona fide// working copy.
-===== Moving a Greenstone installation =====
-For Linux, you will need to uninstall your Greenstone first and then reinstall it in the new location.
-For Windows:
-In the case of GS2.83, if you move your Greenstone2 installation folder to some other location, make sure that you relocate it such that there are no spaces in its new path. For instance, "C:\Program Files\myfolder\greenstone2" contains a space between "Program" and "Files", which is not supported in version 2.83. In future versions of Greenstone, the spaces will not be a problem.
-Once you've moved your Greenstone installation, there are a few further things to do to get it to work again:
-  - Open your Greenstone 2 installation's cgi-bin\gsdlsite.cfg file and change the value for the GSDLHOME property to reflect the new path to your Greenstone installation.
-  - To get the local library server (server.exe) to work from the new location: if your top-level Greenstone installation folder contains the files llssite.cfg and glisite.cfg, delete these. (Note that you should not delete the template files llssite.cfg.in and glisite.cfg.in!) If running the local library server has any issues with Internet Explorer, go to the local library's File>Settings menu and change the Other Browser setting to use Firefox.
-  - To get the Apache web server included with Greenstone to work: delete the file lib\java\log4j.properties. (Doing so will ensure that if you execute the gs2-server.bat file--which launches the Greenstone Server Interface--this properties file will be regenerated with the correct value for gsdlhome.)