RPM repository for lolcat++ — a C++ port of lolcat https://lolcatpp.github.io/rpm/
Find a file
Love 8a24d79527
Revise supported distributions table
Updated the supported distributions table format for clarity.
2026-05-07 14:35:06 +02:00
fedora-43 Update packages to 2.5.5 2026-05-07 12:07:59 +00:00
fedora-44 Update packages to 2.5.5 2026-05-07 12:07:59 +00:00
opensuse-leap-16.0 Update packages to 2.5.5 2026-05-07 12:07:59 +00:00
rhel-9 Update packages to 2.5.5 2026-05-07 12:07:59 +00:00
rhel-10 Update packages to 2.5.5 2026-05-07 12:07:59 +00:00
pubkey.gpg remove orphan pubkey from pubkey.gpg 2026-05-07 14:21:31 +02:00
README.md Revise supported distributions table 2026-05-07 14:35:06 +02:00

lolcat++ RPM Repository

RPM repository for lolcat++ — a C++ port of lolcat.

Hosted via GitHub Pages at https://lolcatpp.github.io/rpm/.

Supported distributions

Family Versions Architectures
Fedora 43, 44 x86_64, aarch64
RHEL / Rocky / Alma 9, 10 x86_64, aarch64
openSUSE Leap 16.0 x86_64, aarch64

Each subpath is its own self-contained RPM repository with repodata/ and a ready-to-use lolcatpp.repo file. The .repo file uses $releasever, so once installed it will follow you across distro upgrades within a family (e.g. Fedora 43 → 44).

Installing

Fedora / RHEL / Rocky / Alma (dnf)

The snippet below detects your distro from /etc/os-release and downloads the matching .repo file:

. /etc/os-release
case "$ID" in
  fedora)               family="fedora-${VERSION_ID}" ;;
  rhel|rocky|almalinux) family="rhel-${VERSION_ID%%.*}" ;;
  *) echo "unsupported distro: $ID"; exit 1 ;;
esac
sudo curl -fsSLo /etc/yum.repos.d/lolcatpp.repo "https://lolcatpp.github.io/rpm/${family}/lolcatpp.repo"
sudo dnf install -y lolcat++

openSUSE Leap (zypper)

. /etc/os-release
sudo zypper addrepo --gpgcheck \
  "https://lolcatpp.github.io/rpm/opensuse-leap-${VERSION_ID}/lolcatpp.repo"
sudo rpm --import https://lolcatpp.github.io/rpm/pubkey.gpg
sudo zypper install lolcat++

How packages get here

Packages are built and published automatically by the release workflow in the main repository when a new tag is pushed. Each supported distribution gets its own RPM built in a matching container, then createrepo_c regenerates the metadata for that distro's subdirectory.

The repository metadata (repomd.xml) is signed with the GPG key in pubkey.gpg.