Select one approach listed here, thus either the official (downstream) EPEL packages repository, or our X2Go EPEL repository and stick to it. Unreleased versions and unofficial (related to the EPEL project) release packages are only available directly from the X2Go project, follow the instructions in the second section to configure your package manager for this.
X2Go packages are provided by the Fedora EPEL project for RHEL and derivative distributions (e.g. CentOS and ScientificLinux). See using EPEL for instructions on how to configure the EPEL repository.
Now you can search for X2Go related package that are now available for your system via YUM:
$ yum search x2go
Congratulations, you are now able to access the X2Go packages. You may continue by installing x2goserver, x2goclient or pyhoca-gui or any other of the available packages.
Download the .repo file and save it to the correct location:
wget -O /etc/yum.repos.d/x2go.repo \ http://packages.x2go.org/epel/x2go.repo
For reference, the file will also be inlined here, with the original information being available on http://packages.x2go.org/epel/x2go.repo:
Edit this file with your preferred editor.
$ editor /etc/yum.repos.d/x2go.repo
As a rule of thumb:
source-labeled repositories are never needed, unless you want to build packages from source.
extras-tagged repositories are always needed.
By default, the
release-labeled repository is enabled and the
nightly-tagged repository is disabled. If you want to use the unreleased, more up-to-date packages, disable the
release-labeled repository and enable the
Note that not all of X2Go may be provided for RHEL/EPEL 5/6, as these distributions are very old and therefore more work-intensive to develop for.
/etc/yum.conf. Standard yum repos do not use the same connection mechanisms as RHN channels.
The packages in this repository can be mirrored via
rsync -avP packages.x2go.org::epel </dest/path/of/local/mirror/epel>