ReviewOS

home-lang/home

Add curl | sh installer for non-pantry users

#13
Closed glennmichael123 opened this 24 days ago · 1 comment
24 days ago

Context

Today's install path is:

git clone https://github.com/home-lang/home.git
cd home
pantry install   # pulls zig 0.16-dev
zig build

That's reasonable for the stacksjs / pantry crowd, but anyone discovering Home from outside has to:

  1. Know what pantry is
  2. Install pantry first
  3. Wait for a from-source build
  4. Pin themselves to whatever Zig dev version we happen to need

For comparison, getting started with Bun, Rust, Deno, or Zig itself is a single shell line. The curl-pipe-sh installer is industry standard for new languages.

Proposal

  • Set up release builds in CI that produce static home binaries for:
    • aarch64-macos, x86_64-macos
    • aarch64-linux, x86_64-linux (musl-static)
    • x86_64-windows (zip with .exe)
  • Publish them as GitHub Release assets, named home-<version>-<target>.tar.gz (predictable URLs)
  • Write an installer script at https://home-lang.org/install.sh (or a similar canonical URL) that:
    • Detects platform
    • Downloads the right tarball from the latest release
    • Verifies a checksum (published alongside the tarballs)
    • Extracts to ~/.home/bin (or ~/.local/bin)
    • Prints PATH instructions
  • Update README to lead with curl -fsSL https://home-lang.org/install.sh | bash
  • Bonus: Homebrew tap (home-lang/tap/home) for Mac users who'd rather not pipe curl into bash

Open questions

  • Where does the install script live? Own repo, or in this one under /install.sh?
  • Domain: home-lang.org? (placeholder above)
  • We're currently pinned to "Zig 0.16-dev." Releases should ship a static home binary so end users don't need any Zig install at all.

Why this matters

  • Removes the largest install-friction wall for outside contributors
  • Makes the "try Home" experience comparable to peer languages
  • Required for any tutorial / blog post we'd want to write or share

Sign in to comment on this issue.