Differences

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

--- wiki:repositories:epel [2016/10/04 09:10]
ionic Make the mix-and-match note a warning and move to the top of the page. Restructure headlines slightly.
+++ 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 derivatives ======
+====== 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 indefinitely run into problems. If you **really** need to switch between repositories, make sure to uninstall all X2Go packages first.</note>
+<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>
+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 [[#adding_the_x2go_repository_to_your_package_system|second section]] to configure your package manager for this.
 ===== Using the Official EPEL Packages Repository =====
@@ Line 9: / Line 13: @@
 <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>
-Now you can search for X2Go related package that are now available for your system via YUM:
+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>
@@ Line 15: / Line 19: @@
 </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
-If you wish to install newer or test versions directly from the X2Go project, follow the instructions below in addition to configuring the EPEL repository.
+<code bash>
+$ dnf search x2go
+</code>
-===== Adding the X2Go Repository to your Package System =====
+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.
-<note>For unsupported, archived EPEL versions, please refer to [[wiki:repositories:archives:EPEL]].</note>
+===== Adding the X2Go Repository to Your Package System =====
-Add the file ''x2go.repo'' to the folder ''/etc/yum.repos.d/''.
+<note>For unsupported, archived EPEL versions, please refer to [[wiki:repositories:archives:epel|EPEL Archives]].</note>
-This can be done using by your preferred editor.
+==== 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 30: / Line 51: @@
 </code>
-A sample content for this file can be found here, with the original information on [[http://packages.x2go.org/epel/x2go.repo]]. Be sure to **edit** this example to match your needs, mostly the ''enabled'' key. ''source''-tagged repositories are only needed if you intend to build packages from source, while ''extras''-labeled repositories are always needed. By default, the ''release''-labeled binaries repository is enabled, while the ''nightly''-labeled binaries repository is disabled. If you want to try newer, unreleased software, disable the ''release''-labeled binaries repository and enable the ''nightly''-labeled binaries repository.
+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 ''nightly''-tagged repository.
+To use Saimaa ESR, enable the ''saimaa''-labeled repository and disable the ''release''- or ''nightly''-tagged repositories.
+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.
+<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>
+$ yum search x2go
+</code>
+or
+<code bash>
+$ dnf search x2go
+</code>
-{{url>http://packages.x2go.org/epel/x2go.repo 720px|EPEL X2Go repository definition file}}
+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 =====
+===== Mirroring This Repository =====
 The packages in this repository can be mirrored via ''rsync'':

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools