Reference
Package channels
Choose a distribution channel and understand how its packages relate to the native release.
For the current stable tools version, see release status. For install commands, see installation.
Choose a channel
Section titled “Choose a channel”| Channel | Platforms | Package or location |
|---|---|---|
| GitHub native archive | The host triples declared by that immutable release | aros-tools releases |
| Homebrew | The matching published Linux or Apple-silicon macOS archive | metaneutrons/tap/aros-tools |
| Signed APT | Debian/Ubuntu on amd64 or arm64, within the binary compatibility floor |
https://deb.metaneutrons.cc |
| AUR | Arch Linux on x86_64 or aarch64 |
aros-tools-bin |
Installation contains the commands and verification procedure. Platform support lists the operating-system compatibility floors and the complete maintained native release matrix. macOS Intel is not a package-manager or archive target.
One native payload per host
Section titled “One native payload per host”The native archive is the canonical binary payload. Debian, Homebrew and AUR packages consume those same measured executables; package channels are not independent compiler builds. Keep the complete suite at one version.
GitHub Releases and package channels can update at different times. Check the channel’s version before upgrading. Prereleases do not update stable channels.
What to verify
Section titled “What to verify”- Native archive: match the host triple, checksum, manifest and signature/ attestation to the selected immutable tag.
- Homebrew: use the documented tap. The formula selects and checks the corresponding archive digest.
- APT: verify the full public signing-key fingerprint, scope it with
signed-by, and allow APT to authenticate the repository metadata. - AUR: review
PKGBUILDand.SRCINFO; check that the source and SHA-256 refer to the intended version’s canonical archive.
The APT key fingerprint and complete verification commands live in the installation guide. Do not bypass an expired signature or checksum mismatch to complete an install.
Updates and failures
Section titled “Updates and failures”Use the package manager that installed the suite. An unavailable package or mismatched version is a channel issue; it is not a reason to mix executables from separate releases. See update and uninstall and installation troubleshooting.