Installation • Contributing Guidelines • Deletion Policy • EoS Schedule • CI status • License

This repository contains spec files and patches used for building RPM packages for EK Public Repository.

Important

Due to the malicious actions of some users, crawlers and AI scrapers, bandwidth to the public repository is limited. However, if you wish to use the repository in your infrastructure, please create a new issue ticket and we will provide you with unique credentials for repository access with higher bandwidth limits.

Installation

sudo dnf install -y https://pkgs.kaos.st/kaos-repo-latest.el$(grep 'CPE_NAME' /etc/os-release | tr -d '"' | cut -d':' -f5).noarch.rpm

Some packages have dependencies from EPEL repository. You could add this repository by following commands:

# Alma Linux / Rocky Linux
sudo dnf install -y epel-release

# Oracle Linux 8
sudo dnf install -y oracle-epel-release-el8

# Oracle Linux 9
sudo dnf install -y oracle-epel-release-el9

# Oracle Linux 10
sudo dnf install -y oracle-epel-release-el10

Some packages have dependencies from CodeReady Builder repository. You can enable this repository by following commands:

# Alma Linux / Rocky Linux
sudo dnf config-manager --set-enabled crb

# Oracle Linux 8
sudo dnf config-manager --set-enabled ol8_codeready_builder

# Oracle Linux 9
sudo dnf config-manager --set-enabled ol9_codeready_builder

# Oracle Linux 10
sudo dnf config-manager --set-enabled ol10_codeready_builder

Contributing Guidelines

If you want to add a new package to the repository, be ready to look after it. It's physically impossible to maintain and keep fresh a large number of packages, especially if you don't use them somewhere.

Also, bibop tests are mandatory for all new packages. It's the only way to test if the package is okay and does not affect other packages in the repository. bibop recipe syntax is easy to learn, so don't be afraid of it.

Please find a minute to check out our main Contributing Guidelines.

Deletion Policy

Security is our first priority. We can't keep an outdated package in our repository for a long time. If a package spec were not updated for the several latest releases (especially with known vulnerabilities) of software, it would be deleted from the repository.

We keep at least the last 5 minor versions (with all releases) of each package. In some cases (e.g. programming languages) we keep more versions of packages. If a version has a critical security vulnerability it may be removed from the repository at any time.

End-of-Support Schedule

EL version	Updates	Repository removal
8.x	1 Jun 2025	31 Dec 2025
9.x	1 Sep 2027	31 Dec 2027
10.x	1 Sep 2030	31 Dec 2030

perfecto and bibop check status

Branch	Status
master
develop

License

Apache License, Version 2.0