Installers & packages¶
Clippy Pet ships as one payload wrapped many ways: the same two files, the same POSIX clippy-pet command, packaged for whatever installs things on your system. Every row below is one of three things:
- live works today from this site or the repository.
- on each release built by CI and attached to every GitHub Release from v1.1.0 on.
- planned designed and often scaffolded, but not published yet. We won't list a command that doesn't work.
| How | Command / file | Status |
|---|---|---|
| One-line install | curl -fsSL https://adammatthewsteinberger.github.io/clippy-pet/install.sh piped to sh | live |
| From a checkout | ./scripts/install.sh | live |
| Runtime tarballs | clippy-pet-<v>.tar.gz / .tgz / .tar.bz2 / .tar.xz / .zip | on each release |
| macOS disk image | Clippy-Pet-<v>.dmg (contains the .app and .pkg) | on each release |
| macOS installer package | Clippy-Pet-<v>.pkg | on each release |
| macOS app | Install Clippy Pet.app | on each release |
| Debian / Ubuntu | clippy-pet_<v>_all.deb | on each release |
| Fedora / RHEL / openSUSE | clippy-pet-<v>-1.noarch.rpm | on each release |
| Alpine | clippy-pet_<v>_noarch.apk | on each release |
| Arch | clippy-pet-<v>-1-any.pkg.tar.zst | on each release |
| Web (v1) sheet | spritesheet-v1.webp for ChatGPT web upload | on each release |
Arch .pkg.tar.xz via makepkg | AUR-style PKGBUILD | planned |
| AppImage | Clippy-Pet-<v>-x86_64.AppImage / -aarch64 | planned |
| Flatpak bundle | Clippy-Pet-<v>.flatpak | planned |
| Snap | clippy-pet_<v>_all.snap | planned |
| Gentoo ebuild | GURU overlay | planned |
| Package managers | Homebrew, MacPorts, Nix, apt repo, COPR, OBS, AUR, aports, Snap Store, Flathub, conda-forge, vcpkg, conan | planned (details) |
About that first release
Rows marked on each release depend on a tagged release existing. v1.1.0 is the first packaged release; if the releases page is still empty when you read this, the one-liner will politely tell you so and the from-checkout path still works.
Pages in this section¶
- One-line install & tarballs: what
install.shdoes, line by line, and the tarball layout. - macOS:
.dmg,.pkg,.app, signing/notarization status, Homebrew and MacPorts plans. - Linux:
.deb,.rpm,.apk, Arch, and what each package puts where; AppImage/Flatpak/Snap/Nix plans. - Package managers: the per-ecosystem publication path we're following and how far along each is.
- Verify downloads:
SHA256SUMS, cosign, GitHub attestations, GPG and apk keys.
Design in one paragraph¶
Pets are per-user (~/.codex/pets/), and no system package manager is allowed to write into your home directory. So every system package installs the payload under <prefix>/share/clippy-pet/ plus a 400-line POSIX-sh CLI, and the CLI copies the payload into your home when you (or a login autostart entry you opt into) run it. GUI installers and the one-liner talk to your home directly. Same files, same checksums, everywhere. The packaging runbook has the whole rationale.