Differences

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

--- wiki:repositories:epel [2013/12/28 17:18]
sunweaver
+++ wiki:repositories:epel [2017/12/12 08:29] (current)
ionic Add instructions for Saimaa ESR.
@@ Line 1: / Line 1: @@
-====== X2Go Packages for Redhat Enterprise Linux and alike (EPEL) ======
+====== X2Go Packages for Redhat Enterprise Linux and Derivatives ======
+<note warning>Do not mix-and-match packages from the official EPEL repository with packages from the X2Go EPEL repository. Due to differing version number schemes, you will definitely run into problems. If you **really** need to switch between repositories, make sure to uninstall all X2Go packages first.</note>
-To get started you'll need to configure your local system to access the official X2Go EPEL repository. Please keep in mind that this installation manual will guide you through the installation on a RHEL-6 based system. The repository will basically offer you packages for i386 and amd64 architectures.
+Select one approach listed here, thus either the official (downstream) EPEL packages repository, or our X2Go EPEL repository and stick to it.
-First, make your system ready for [[http://fedoraproject.org/wiki/EPEL/FAQ#Using_EPEL|using EPEL-6]]. **Note:** By adding EPEL package archives to your system you surpass a point of no return. Only do this if you are sure you want to do this.
+Unreleased versions and unofficial (related to the EPEL project) release packages are only available directly from the X2Go project, follow the instructions in the [[#adding_the_x2go_repository_to_your_package_system|second section]] to configure your package manager for this.
+===== Using the Official EPEL Packages Repository =====
+X2Go packages are provided by the Fedora EPEL project for RHEL and derivative distributions (e.g. CentOS and ScientificLinux). See [[http://fedoraproject.org/wiki/EPEL/FAQ#Using_EPEL|using EPEL]] for instructions on how to configure the EPEL repository.
-Then, please add the file ''x2go.repo'' to the folder ''/etc/yum.repos.d/''.
+<note>The X2Go Project can not provide complete support for these packages. While the current downstream EPEL maintainer is part of the [[doc:organigram|X2Go development team]], X2Go developers generally do not have access to the official EPEL repository. Problems are best handled downstream.</note>
-This can be done using by your preferred editor.
+Now you can search for X2Go related packages that are now available for your system via ''yum'' or ''dnf'', whatever is most appropriate for your system:
+<code bash>
+$ yum search x2go
+</code>
+or
+<code bash>
+$ dnf search x2go
+</code>
+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.
+===== Adding the X2Go Repository to Your Package System =====
+<note>For unsupported, archived EPEL versions, please refer to [[wiki:repositories:archives:epel|EPEL Archives]].</note>
+==== Base Installation ====
+Download the .repo file and save it to the correct location:
+<code bash>
+wget -O /etc/yum.repos.d/x2go.repo \
+ https://packages.x2go.org/epel/x2go.repo
+</code>
+For reference, the file will also be inlined here, with the original information being available on [[https://packages.x2go.org/epel/x2go.repo]]:
+{{url>https://packages.x2go.org/epel/x2go.repo 720px|EPEL X2Go repository definition file}}
+==== Customization ====
+Edit this file with your preferred editor.
 <code bash>
@@ Line 15: / Line 51: @@
 </code>
-Then add the X2Go repository to your YUM setup:
+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.
-<file - x2go.repo>
+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 ''nightly''-tagged repository.
-[x2go-releases]
-name=Upstream X2Go Packages (nightly builds)
-baseurl=http://packages.x2go.org/epel/6/heuler/$basearch
-gpgcheck=0
-enabled=1
-protect=0
-[x2go-extras]er te
+To use Saimaa ESR, enable the ''saimaa''-labeled repository and disable the ''release''- or ''nightly''-tagged repositories.
-name=Upstream X2Go Packages (extra packages)
-baseurl=http://packages.x2go.org/epel/6/extras/$basearch
-gpgcheck=0
-enabled=1
-protect=0
-</file>
+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.
-Now you can search for X2Go related package that are now available for your system via YUM:
+<note>If you are behind a proxy, make sure the proxy is defined in ''/etc/yum.conf''. Standard yum repos do not use the same connection mechanisms as RHN channels.</note>
+==== Post-Addition Test ====
+Now you can search for X2Go related packages that are now available for your system via ''yum'' or ''dnf'', whatever is appropriate for your system:
 <code bash>
@@ Line 40: / Line 69: @@
 </code>
-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.
+or
+<code bash>
+$ dnf search x2go
+</code>
+Congratulations, you are now able to access the X2Go packages. You may continue by installing ''x2goserver-xsession'', ''x2goclient'' or ''pyhoca-gui'' or any other of the available packages.
+===== Mirroring This Repository =====
+The packages in this repository can be mirrored via ''rsync'':
+<code>
+rsync -avP packages.x2go.org::epel </dest/path/of/local/mirror/epel>
+</code>

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools