Table of Contents
This chapter assumes that you have already succesfully installed TinyFugue in your system and you know how to use it (basic commands, loading of macros, etc.) It is also assumed that you know how to use your operating system of choice, be it some flavour of UNIX or Windows, although some parts of the instructions are given in step-by-step manner.
Throughout this manual, when GgrTF files are referenced in configuration examples etc., I have used "ggrtf/" -directory as path where the script files are located. You may need to substitute it with whatever you have installed your copy of GgrTF in.
There are basically two ways how to get GgrTF, release packages and the Subversion-repository. Releases are considered as stable snapshots, which should be relatively bug-free, but releases are done somewhat infrequently and at least in this phase we don't backport bugfixes to release versions.
If you are unsure which version to choose, use the latest packaged release.
To get the latest stable version, head to the downloads-section of GgrTF's homepage and pick either the newest tarball (*.tar.gz) or zip-archive (*.zip):
*.tar.gz packages are for UNIX-style systems, such as Linux, *BSD, etc. Please note that the ZIP-packages are meant for Windows only and WILL NOT WORK under UNIX or OS X version of TinyFugue!
*.zip packages are for Windows version of TinyFugue (the files have been converted to CRLF line endings.)
Both package types also have equivalent PGP/GnuPG signature files (*.asc), which can be used to cryptographically verify the authenticity of files.
Another way to get GgrTF is to go to the very source, the development source repository. This repository contains the latest bleeding edge features, but is also a fast moving target. Changes are directly "pushed" (committed) by developers almost in real time, sometimes what you download may be severely broken. Also the documentation will not be updated for every little change, so you may have to figure out and work around possible backward incompatibilities yourself.
New features and new bugfixes may sometimes be worth taking the risk. On the other hand, it is all up to what you want and whether you can manage to handle the possibly arising problems.
We utilize Subversion (SVN) for GgrTF's version management. Subversion is a freely available Open Source version control system, for which there are clients available for most common platforms, including Windows, Linux and other flavours of UNIX.
GgrTF's Subversion repository is graciously hosted by Jarkko Vääräniemi (Jeskko) at Pupunen.net, and is available from following location:
Trunk-repository, all the latest stuff goes here:
You can browse the repository more easily via Pupunen.net's ViewCVS interface:
You can download ("checkout") the GgrTF repository with command line Subversion client with following command:
svn co http://svn.pupunen.net/public/ggrtf/trunk/ ggrtf
In which "co" stands for "checkout", after which comes URL of the repository and finally path to directory ("ggrtf") which the files will be checked out into.
You will most probably want to download the repository to some specific place, personally I prefer to use $HOME/ggrtf/ (aka "ggrtf/" subdirectory under user's homedir) under UNIX.
After you have checked out your own copy of GgrTF's code repository, you usually wish to periodically update it. This is done easily with Subversion's "update" command. First go to the repository directory and then issue "svn update" or the shorthand "svn up", as follows:
cd ggrtf svn up
If you have made changes to the files, Subversion tries to merge them with changes that have occured in the main repository. Sometimes the changes may be interfering with each other and this causes a merging error. You must fix these problems by hand, please refer to Subversion documentation for more information and tips.