Install the .rpm or .deb files like you would install any of these packages: rpm -i glGo-xxx.rpm or dpkg -i glGo-xxx.deb. If you use the .tar.gz archive, unpack it somewhere and run the glGo.install script. To uninstall, run glGo.remove.

Basically it does not matter which of the installers you use. Take the one most fitting for your distribution. They all install exactly the same files.

The user configuration is found in $HOME/.glGo. Please remove this directory manually after uninstalling.

In any case you require OpenGL libraries installed, they are installed together with your hardware driver. In worst case, install the Mesa libraries for software-only rendering, but this is not recommended

glGo on Linux uses the GTK-2 toolkit. This requires a couple of libraries available. They should be installed together with GTK-2 from your distribution. If you use the Gnome desktop, you already have all of these libraries.

You need the following SDL libraries: libsdl, libsdl_ttf and libsdl_image. They are all available with all major Linux distributions. If you don't have them already installed, get them from your distribution. In case try ldd glGo to check the dependencies.

You need the Python 2.4 runtime library installed (shared library). Python should be included in almost every Linux distribution.

For the sound system you need either the OpenAL or the SDL_mixer runtime libraries installed. They should be included in every Linux distribution. Unlike Windows, OpenAL is not included in the Linux glGo installer, as it is to be preferred to use your Linux distribution version. If neither libopenal nor libSDL_mixer are available, glGo should still run, but without sound output.

Here are the most important dependencies. Nothing special, but you might need to install some library from your distribution.

Optional for sound output:

If you want to play with GNU Go, please install it from your distribution, it is included in almost any, or compile it yourself. Make sure the gnugo binary is found in your PATH environment, so glGo will find it. Common locations are /usr/local/bin, /usr/bin or /usr/games/bin.

If you installed glGo in an unusual directory, you can use the “-s” commandline option to point to the shared data directory. Example: glGo -s /home/foobar/myprogs/coolapps/glGo/share. Another possibility is to set the environment variable “GLGO_SHARED_PATH”, for example in bash: export GLGO_SHARED_PATH=/home/foobar/myprogs/coolapps/glGo/share. The “-s” option has higher priority than the environment variable. If neither is given glGo will search for the shared directory in the folder the binary is located, /usr/share/games, /usr, /usr/local, /usr/local/share/games, /opt, $HOME, $HOME/glGo and $HOME/.local/share/glGo. If no shared directory is found, glGo will fail to start. If you keep the default directories in the installation and don't move files around later, you do not need to worry about this.

glGo support libraries (, and are located in /usr/lib/games/glGo. If you really need to move this directory around, you need to tell glGo the location of these libraries. You can do this by setting the environment LD_LIBRARY_PATH to the new directory.


Additionally to rpm, deb and tar.gz format, glGo for Linux is available as alternative installer using Autopackage, a new multi-distribution installation system which does not rely on the distribution specific formats. Unlike rpm, deb and the tar.gz installer, Autopackage offers the possibility to install glGo as user without root access.

Execute the glGo-xxxx.package file in a terminal or from Nautilus/Konqueror. Depending on your current environment, a GTK, Qt or ncurses frontend will start. If this is the first autopackage you are installing on your Linux system, it will require some additional libraries. This is an automated process and only needed once. When the autopackage system has been installed, upgrading existing packages or installing new ones won't require this procedure again.

Autopackage will prompt you for the root password. If you provide the password, glGo will install into /usr. If not, glGo is installed into $HOME/.local. These are the default locations and can be overwritten using the --prefix parameter. See "glGo-xxxx.package --help" for details.

The installer will check your system for the availability of required libraries. If any are missing, please install them from your Linux distribution.


Autopackage gotchas

When installing into userspace, the glGo binary will be in $HOME/.local/bin, which is by default not included into the PATH, so starting glGo would fail. Autopackage automatically appends a line to .bashrc, which adds $HOME/.local/bin to your PATH. However, on some Linux distributions .bashrc is not read when logging into your desktop from gdm or kdm. Hence, glGo will start from the terminal, but fail when starting from the menu entry or a desktop icon. The workaround I use on my system is to copy the line autopackage appended to .bashrc to a new file .gnomerc, which will be read when Gnome starts up. There should be some similar trick with KDE or other desktops.

To deinstall glGo, use package remove glGo.