Test beta or Subversion versions

To help GCstar’s development, you may test new versions. They could be beta versions, that are released, but announced as potentially unstable ones. Or you may try the current version from Subversion (referred sometimes as SVN).

As this may lead to some problems, you could want to perform these tests without interfering with your previous installation and your actual collections.

Get new versions

| Top |


The beta versions are delivered with official version. Then you may find it in the download repository. The more recent ones are on top of the listing.


You will find all the information on the Subversion repository page on Gna!. You could also directly download the daily snapshot if you don’t want to bother with Subversion.

Please note that these versions may be more unstable that the beta ones. They may even fail to launch (but this should not happen).

Perform tests

| Top |

Now you will be able to test GCstar’s features. Just try to perform some operations and check if the results corresponds to what you expected. If you find any problem, please report it in the forum dedicated to bug reports


We will first prepare an environment where the tests will be performed without impacting other versions.

Create a directory where the tests will take place. It could be gcstar, in subdirectory dev in your home direction. But anything else could be used. Then go into this directory.

mkdir -p ~/dev/gcstar/
cd ~/dev/gcstar/

Extract all of the GCstar’s sources you got in previous step here. If you have some subdirectories, move up all the files so you directly have the directories bin, lib and share in your current directory. If you downloaded a beta version, this should be done like this:

tar zxf gcstar-X.Y.Z.beta1.tar.gz
mv gcstar/* .
rmdir gcstar

We will now create a new directory that will store all of the GCstar’s configuration. Then we won’t change anything to installed version. The important part comes now. You need to set the environment variable XDG_CONFIG_HOME to tell GCstar where it should look for your configuration. In this directory, it will create a subdirectory gcstar to store the actual files.

mkdir config
export XDG_CONFIG_HOME=`pwd`/config

Launch GCstar

You won’t need anything else that what is required to use official version. No *-devel package or similar is needed. Then, if you are already using GCstar, you won’t have anything to do. If you are new to this application, read the page about installation.

Just go into subdirectory bin and launch gcstar using perl interpreter.

cd bin
perl ./gcstar

Script automating these tasks

| Top |

Here is a small Perl script that does everything that have been mentioned before:


Current version relies on some command-line tools such as tar or cp. So it may not work on systems without these tools.

You may want to edit it to change the path where everything will be extracted. It’s set in the variable BASE_DIR on top of the file. This variable should not contain shell-specific characters such as ~.

Then launch it for the first time with the option -d with a version. It will download the corresponding version, extract it and launch GCstar with a configuration different from the one you could already have.

Here are some examples:

./testgcstar -d 1.1.1
./testgcstar -d 1.2.0.beta1
./testgcstar -d SVN

The first command downloads and launch GCstar 1.1.1. The second one do the same for version 1.2.0-beta. The last one uses a special value. When this is used, the current Subversion snapshot will be used. You can use CVS instead of SVN to keep backward compatibility, but it will also download the Subversion snapshot.

If you wish to launch the version you already downloaded, just launch this tool without any parameter:

Keep in mind that if you did some changes locally in GCstar’s code, they will be lost the next time you use this tool with -d option.

en/test.txt · Last modified: 26/07/2008 12:34 by Tian

Should you have a problem using GCstar, you can open a bug report or request some support on GCstar forums.