From Fedora Project Wiki

< SIGs‎ | KDE

 
(5 intermediate revisions by 3 users not shown)
Line 4: Line 4:
== Installation ==
== Installation ==


=== Install epel-release ===
=== Install / Enable EPEL ===
Follow the EPEL Quckstart Instructions. [https://docs.fedoraproject.org/en-US/epel/#_quickstart]


    dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
=== Install KDE ===
* dnf group install kde-desktop-environment


=== Enable codeready-builder or PowerTools ===
or
If RHEL 8:
* subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms
If CentOS 8:
*  dnf config-manager --enable PowerTools


=== Install KDE ===
* dnf group install kde-desktop
* dnf group install kde-desktop
* (Optional) dnf group install kde-apps
* (Optional) dnf group install kde-media
* (Optional) dnf group install kde-media
* (Optional) dnf group install kde-apps
* (Optional) dnf group install kde-education
* (Optional) dnf install okular
* (Optional) dnf install okular
* (Optional) dnf group install kde-software-development
* (Optional) dnf group install kf5-software-development


=== (Optional if Workstation already installed) Set sddm as desktop manager ===
=== (Optional if Workstation already installed) Set sddm as desktop manager ===
Line 36: Line 36:


== Update Schedule ==
== Update Schedule ==
EPEL Users are running on a stable Enterprise Linux, and expect stability.  KDE is a fairly fast updating desktop. If it isn't updated fairly regularly, it is hard to keep up with bugs and security issues.  After discussion, the KDE Sig decided that a once a year update would give users the stability they want, along with the updates they need.
EPEL Users are running on a stable Enterprise Linux, and expect stability.  KDE is a fairly fast updating desktop. If it isn't updated fairly regularly, it is hard to keep up with bugs and security issues.  After discussion, the KDE SIG decided that twice a year update would give users the stability they want, along with the updates they need.
 
=== Update Timing EPEL 8 ===
EPEL 8 KDE Plasma Desktop is going to stay at the releases that they currently are at.  We will backport major security fixes.  Bugs and bugfixes will be best effort.  But we will not do any across the board updates.
 
This is due to the older libraries in RHEL 8.  We've hit the limit that the newer KDE versions can run on the older libraries.


=== Update Timing ===
=== Update Timing EPEL 9+ ===
Plasma releases will be synchronized from Fedora to EPEL after each spring release (e.g., F36, F38, and so on)
Plasma releases will be synchronized from Fedora to EPEL after each Fedora release (e.g., F38, F39, and so on) The update will correspond with a RHEL release.


The once a year update will correspond with a RHEL release.  It will first go into the epel-next repo, and be built on Stream.  When the corresponding RHEL release is released, all the epel-next packages will be rebuilt on regular epel.
The update will first go into the epel-next repo, and be built on CentOS Stream.  When the corresponding RHEL release is released, all the epel-next packages will be rebuilt on regular epel.


=== Security and Bugfixes ===
=== Security and Bugfixes ===
This once a year update schedule will catch most of the major bugs and security issues.  But there will be a period of time toward the end of the year when this gets difficult.  The KDE SIG will give a best-effort attempt to backport fixes from future stable releases as needed, but if not possible, rebasing Plasma remains an option.
This twice a year update schedule will catch most of the major bugs and security issues.  But there will be times when this gets difficult, particularly in the middle of the year.  The KDE SIG will give a best-effort attempt to backport fixes from future stable releases as needed, but if not possible, rebasing Plasma remains an option.


=== QT updates in RHEL ===
=== Qt updates in RHEL ===
RHEL coordination for Qt will be included as part of this effort to align to spring releases
RHEL coordination for Qt will be included as part of this effort to align to RHEL releases.

Latest revision as of 16:54, 20 July 2023

KDE on EPEL

KDE was part of RHEL up until RHEL 8. At that point the majority of KDE was removed, with only some qt5 packages left. This allowed the EPEL community to build KDE Plasma Desktop in EPEL.

Installation

Install / Enable EPEL

Follow the EPEL Quckstart Instructions. [1]

Install KDE

  • dnf group install kde-desktop-environment

or

  • dnf group install kde-desktop
  • (Optional) dnf group install kde-apps
  • (Optional) dnf group install kde-media
  • (Optional) dnf group install kde-education
  • (Optional) dnf install okular
  • (Optional) dnf group install kde-software-development
  • (Optional) dnf group install kf5-software-development

(Optional if Workstation already installed) Set sddm as desktop manager

  • systemctl set-default graphical.target
  • dnf install sddm\*
  • systemctl enable sddm -f
  • reboot

(If Workstation already installed, and didn't enable sddm)

  • systemctl reload gdm

(Optional) Install apps via flatpak

Update Schedule

EPEL Users are running on a stable Enterprise Linux, and expect stability. KDE is a fairly fast updating desktop. If it isn't updated fairly regularly, it is hard to keep up with bugs and security issues. After discussion, the KDE SIG decided that twice a year update would give users the stability they want, along with the updates they need.

Update Timing EPEL 8

EPEL 8 KDE Plasma Desktop is going to stay at the releases that they currently are at. We will backport major security fixes. Bugs and bugfixes will be best effort. But we will not do any across the board updates.

This is due to the older libraries in RHEL 8. We've hit the limit that the newer KDE versions can run on the older libraries.

Update Timing EPEL 9+

Plasma releases will be synchronized from Fedora to EPEL after each Fedora release (e.g., F38, F39, and so on) The update will correspond with a RHEL release.

The update will first go into the epel-next repo, and be built on CentOS Stream. When the corresponding RHEL release is released, all the epel-next packages will be rebuilt on regular epel.

Security and Bugfixes

This twice a year update schedule will catch most of the major bugs and security issues. But there will be times when this gets difficult, particularly in the middle of the year. The KDE SIG will give a best-effort attempt to backport fixes from future stable releases as needed, but if not possible, rebasing Plasma remains an option.

Qt updates in RHEL

RHEL coordination for Qt will be included as part of this effort to align to RHEL releases.