← All posts

What's next — pacman repo, source transparency, and the next wave of work

2026-04-21 Cerberix Linux

Three days in, the first wave of launch-week feedback is landing, the ISO is mirrored globally, and it's time to outline what's coming next. This isn't a wishlist — it's the concrete work queue.

A dedicated pacman repository

The single most important piece of infrastructure Cerberix doesn't have yet is its own signed pacman repository. Right now, if a bug in Cerberix Shield or a tuning improvement in the installer needs to reach users, the only distribution mechanism is cutting a new ISO. That's slow, wasteful, and out of line with what users rightly expect from an Arch-based system.

The plan:

repo.cerberix.org/x86_64/
  cerberix-shield-<version>.pkg.tar.zst
  cerberix-connect-<version>.pkg.tar.zst
  cerberix-install-<version>.pkg.tar.zst
  cerberix-fw-setup-<version>.pkg.tar.zst
  cerberix-firstboot-<version>.pkg.tar.zst
  cerberix-backgrounds-<version>.pkg.tar.zst
  cerberix-branding-<version>.pkg.tar.zst
  cerberix.db.tar.gz
  ... and detached .sig files for each

The repo will be hosted through SourceForge's global mirror network (the same infrastructure that serves the ISO) and signed with the same GPG key published at cerberix.org/gpg.asc. Every Cerberix install will ship with a [cerberix] section already in /etc/pacman.conf, so pacman -Syu Just Works from day one.

Practical result: a Shield fix no longer requires a reinstall. It becomes a 30-second pacman -Syu for everyone.

Beyond the Cerberix-branded tooling, the repo will also carry a small set of in-house utilities (netscope, swapwatch, and others currently living only in /usr/local/bin/ on the maintainer's own systems). Shipping them as proper packages makes them installable, upgradeable, and removable like any other Arch software.

Source transparency on GitHub

Cerberix is already reproducible — the build is a short Bash script, the rootfs is a simple overlay, and the ISO is signed. What's missing is a public, read-only source tree so anyone curious can inspect the code without a download.

A GitHub repo is coming, strictly as an inspection mirror. Rules:

This split — transparent source on GitHub, artifacts on infrastructure we own — keeps Cerberix's distribution independent of any single platform's policy changes.

Smaller items in the queue

What's intentionally not on the list


If any of this is broken or misaligned with what you want from a security-focused distribution, tell us — bugs@cerberix.org for reproducible issues, hello@cerberix.org for everything else.

The next release-notes post will land when the first point-release ships. Subscribe via RSS if you want to be notified.