Install Zacess Scenes
From Zacess Scenes v1.1.0. Edit this page on GitHub
| System | Shortest route |
|---|---|
| macOS and Linux | Homebrew |
| Windows | winget |
| Anywhere with a Rust toolchain | Cargo |
| Anywhere else and any machine without a package manager | A release archive |
Homebrew (macOS and Linux)
brew install zacesshq/tap/zacess-scenesThe formula installs the release binary for the machine (Apple silicon, Intel, Linux on x86-64 or
ARM64) after Homebrew has checked it against the checksum recorded in the formula. brew upgrade zacess-scenes moves to a newer release.
winget (Windows)
winget install Zacess.ScenesEach release is submitted to the winget community repository once its files are attached, so the newest version can take a day or two to reach winget. The release archive below is current straight away.
Cargo (crates.io)
cargo install --locked zacess-scenesRust 1.85 or later and a C compiler, since Lua 5.4 is built into the program. The dependencies are crossterm, mlua with its own copy of Lua and signal-hook on Unix. The crate on crates.io carries the code, the docs and the licence; the gallery stills stay here.
A release archive
Each release carries a built binary for:
| File | System |
|---|---|
zacess-scenes-<tag>-aarch64-apple-darwin.tar.gz |
macOS on Apple silicon |
zacess-scenes-<tag>-x86_64-apple-darwin.tar.gz |
macOS on Intel |
zacess-scenes-<tag>-x86_64-unknown-linux-musl.tar.gz |
Linux on x86-64, no shared libraries needed |
zacess-scenes-<tag>-aarch64-unknown-linux-musl.tar.gz |
Linux on ARM64, no shared libraries needed |
zacess-scenes-<tag>-x86_64-pc-windows-msvc.zip |
Windows on x86-64 |
Each archive has a .sha256 file beside it. Download both into the same folder, check the sum,
unpack the archive and put zacess-scenes (or zacess-scenes.exe) somewhere on your PATH.
On macOS:
shasum -a 256 -c zacess-scenes-v1.1.0-aarch64-apple-darwin.tar.gz.sha256
tar -xzf zacess-scenes-v1.1.0-aarch64-apple-darwin.tar.gz
install -m 755 zacess-scenes-v1.1.0-aarch64-apple-darwin/zacess-scenes ~/.local/bin/On Linux:
sha256sum -c zacess-scenes-v1.1.0-x86_64-unknown-linux-musl.tar.gz.sha256
tar -xzf zacess-scenes-v1.1.0-x86_64-unknown-linux-musl.tar.gz
install -m 755 zacess-scenes-v1.1.0-x86_64-unknown-linux-musl/zacess-scenes ~/.local/bin/On Windows, in PowerShell, the two hashes printed must match:
(Get-FileHash .\zacess-scenes-v1.1.0-x86_64-pc-windows-msvc.zip).Hash
Get-Content .\zacess-scenes-v1.1.0-x86_64-pc-windows-msvc.zip.sha256
Expand-Archive .\zacess-scenes-v1.1.0-x86_64-pc-windows-msvc.zip -DestinationPath .From a script
A setup script can keep a machine on the newest release without a package manager. The release
names follow one pattern, so the script asks GitHub for the latest tag, downloads the archive for
its own platform with the .sha256 file and checks the sum before installing:
tag="$(curl -fsSL https://api.github.com/repos/zacesshq/scenes/releases/latest | sed -n 's/.*"tag_name": *"\(v[0-9.]*\)".*/\1/p')"
target=aarch64-apple-darwin # or x86_64-apple-darwin, x86_64-unknown-linux-musl, aarch64-unknown-linux-musl
name="zacess-scenes-$tag-$target"
curl -fsSLO "https://github.com/zacesshq/scenes/releases/download/$tag/$name.tar.gz"
curl -fsSLO "https://github.com/zacesshq/scenes/releases/download/$tag/$name.tar.gz.sha256"
shasum -a 256 -c "$name.tar.gz.sha256" # sha256sum -c on Linux
tar -xzf "$name.tar.gz"
install -m 755 "$name/zacess-scenes" ~/.local/bin/zacess-scenes --version prints the installed version, so a script can skip the download when it
already matches the tag.