soar mit Homebrew installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• soar

Projektgeschichte

The first public GitHub release, v0.1.0, appeared on 2024-10-10 with core package-manager commands for search, install, update, remove, query, run, use, symlink ownership checks, configuration loading, and installed-package tracking.

By v0.3.0 on 2024-10-26, Soar added AppImage integration, portable home and config directory support, health checks, terminal image display support, and package metadata improvements.

The official release notes describe the v0.10 line as adding GitHub and GitLab release sources, build-from-source support, lifecycle hooks, Landlock sandboxing, and system-wide installs. The v0.12 line consolidated repositories around the unified soarpkgs repository and added repository-management CLI features, fuzzy search, metadata signature verification, local-file installs, and shell completions.

Adoptionsgeschichte

Soar is distributed as a single statically linked executable with an install script, and the official docs position it for use across Linux distributions including Debian, Arch, Fedora, and Alpine.

Homebrew includes the package as brew:soar, while upstream documentation points users to the official soarpkgs repository as the default package source.

Wie es verwendet wird

Typical usage starts by running the official install script, adding the Soar bin path to PATH, and installing packages with commands such as `soar install neovim`.

Soar supports imperative package operations, repository configuration in `~/.config/soar/config.toml`, declarative package management through `~/.config/soar/packages.toml`, direct GitHub and GitLab release sources, custom URL packages, hooks, sandboxing, profiles, and optional system mode.

Warum Paket-Nerds sich dafür interessieren

Soar matters to package-manager users because it explores a distro-independent model centered on portable binaries rather than distro-native build recipes, while still keeping package metadata, repository signatures, local install state, declarative manifests, and update behavior under one CLI.

Its relationship with soarpkgs gives it a Homebrew-like split between package manager and package repository, but targeted at static binaries, AppImages, FlatImages, RunImages, and similar portable Linux formats.

Zeitleiste

• 2024-10-10: Soar v0.1.0 released with core package-manager commands.
• 2024-10-11: v0.2.0 added arbitrary file downloads and remote binary runs.
• 2024-10-26: v0.3.0 added AppImage integration and portable home/config support.
• 2025-01-24: v0.10.3 continued the v0.10 line that official notes associate with GitHub/GitLab sources, builds, hooks, sandboxing, and system-wide installs.
• 2026-02-24: v0.12.0 consolidated repositories around the unified soarpkgs repository.
• 2026-06-27: GitHub listed Soar v0.12.6 as the latest release.

Related projects

• soarpkgs is the official package repository that provides package metadata consumed by Soar.
• pkgforge hosts the Soar project and related package infrastructure.

Quellen

• Official CLI reference: https://soar.qaidvoid.dev/cli-reference
• Official GitHub releases: https://github.com/pkgforge/soar/releases
• Official configuration docs: https://soar.qaidvoid.dev/configuration
• Official declarative package docs: https://soar.qaidvoid.dev/declarative
• Official docs: https://soar.qaidvoid.dev/
• Official release notes: https://soar.qaidvoid.dev/releases