GitHub Release-backed Debian packages, RADPx .radpm metadata, and generated documentation for RADLib, RADBard, RadBuild, RADPx OS, and related Radical Computer Technologies releases.
Stable packages stay pinned to known runtime lines; experimental packages move faster for active beta work.
Use stable for release-pinned packages such as the RADLib 0.1.0 line. Debian metadata is signed and hosted through GitHub Releases.
sudo tee /etc/apt/sources.list.d/radical-computer-technologies.sources >/dev/null <<'EOF'
Types: deb
URIs: https://github.com/Radical-Computer-Technologies/RadicalPackages/releases/download/apt-stable
Suites: ./
Signed-By: /etc/apt/keyrings/radical-packages.gpg
Architectures: amd64 arm64
EOF
sudo apt update
Experimental Repository
Use experimental for beta applications and development releases before promotion to stable, including RadBuild 0.2.2-beta.1 and RADPx OS Crimson assets.
sudo tee /etc/apt/sources.list.d/radical-computer-technologies-experimental.sources >/dev/null <<'EOF'
Types: deb
URIs: https://github.com/Radical-Computer-Technologies/RadicalPackages/releases/download/apt-experimental
Suites: ./
Signed-By: /etc/apt/keyrings/radical-packages.gpg
Architectures: amd64 arm64
EOF
sudo apt update
Install The Signing Key
Install the RadicalPackages public key before adding either APT channel.
After adding the stable or experimental APT channel, install the package family you need from the catalog. Stable is for release-pinned packages; experimental is for beta and active development releases.