Package managers¶
Each ecosystem has its own author path, its own review, and its own timeline. We're following the normal one for each rather than side-loading, which means most rows are still planned as of this writing. This table is the source of truth; when a row goes live, its command will be added to the Install page.
| Manager | Command (once live) | Channel we're using | Status |
|---|---|---|---|
| Homebrew | brew install adammatthewsteinberger/tap/clippy-pet | Tap adammatthewsteinberger/homebrew-tap (repo exists, formula written); homebrew-core once notable | planned |
| MacPorts | sudo port install clippy-pet | PR to macports-ports (sysutils/clippy-pet, noarch) | planned |
| Nix | nix profile install github:adammatthewsteinberger/clippy-pet | flake.nix in-repo + Home Manager module; nixpkgs pkgs/by-name PR | planned |
| apt (Debian, Ubuntu, …) | deb [signed-by=…] https://adammatthewsteinberger.github.io/clippy-pet/apt stable main | Signed static repo on GitHub Pages (GPG key published); Launchpad PPA; Debian ITP long-term | planned |
| dnf (Fedora, RHEL) | dnf copr enable adammatthewsteinberger/clippy-pet | COPR; Pages rpm-md repo; Fedora review long-term | planned |
| zypper (openSUSE) | via OBS home:adammatthewsteinberger:clippy-pet | OBS; Factory later | planned |
| pacman (Arch) | yay -S clippy-pet | AUR (arch=any, source = release tarball) | planned |
| apk (Alpine) | Pages apk repo; testing/clippy-pet in aports | Self-hosted signed repo + aports MR | planned |
| Snap | sudo snap install clippy-pet | Snap Store, edge → stable; needs personal-files approval | planned |
| Flatpak | flatpak install clippy-pet.flatpakref | Self-hosted OSTree repo on Pages; Flathub PR attempted | planned |
| conda / mamba | conda install -c conda-forge clippy-pet | conda-forge staged-recipes (noarch: generic); interim Pages channel | planned |
| Gentoo | emerge app-misc/clippy-pet | GURU overlay | planned |
| vcpkg | vcpkg install clippy-pet --overlay-ports=… | In-repo registry; upstream PR likely declined (data-only) | planned |
| conan | conan create . | conanfile.py; conan-center likely declines (data-only) | planned |
Why so many, and why so honest¶
Two reasons. First, the whole point of a pet is that it's there: if you're on NixOS you shouldn't have to curl | sh. Second, this table doubles as the project's own to-do list, and lying to ourselves on it doesn't help anyone. Each row is one PR, account, or review queue away, and each has a maintainer runbook entry in Packaging.
If you maintain packages for one of these ecosystems and want to help land a row, open a discussion; the recipes are drafted and we'd love a second pair of eyes.