Package for Nix, NixOS, and Guix, and document installing from them

[UnbreakableMJ]

None of the three packaging definitions could build. Each fetches a v0.1.0 git tag that does not exist, with lib.fakeHash / all-zero base32 placeholders — so Vacuum could not be installed from a package on any system. There was no flake, and the README offered only cargo install --path.

One package definition, two entry points

packaging/default.nix now takes optional src and version arguments and reads its dependencies from the committed Cargo.lock. The flake passes src = self, so a checkout builds today without waiting for a release tag, and there is no cargoHash to regenerate on every dependency bump. One definition serves both the flake and a release build, rather than the two drifting apart.

The flake exposes packages, apps, checks, devShells (default + docs), and nixosModules.default with programs.vacuum.enable. The default shell supplies the toolchain from nixpkgs rather than rustup — rustup would download a second complete toolchain (~1.5 GB) for a pin this workspace does not need. This is not hypothetical: on the maintainer's NixOS host every rustup toolchain fails with cannot execute: required file not found, so the devShell is the only working way to build here.

Guix

manifest.scm gives Guix users the same environment, naming packages by specification so it need not track which module each currently lives in. packaging/guix.scm grows the Texinfo build and install-info step that Standard §8.6 requires.

It still cannot build, and says so plainly in the file, the README, and the manual rather than leaving someone to discover it: cargo-build-system resolves dependencies through #:cargo-inputs, and this workspace locks 191 crates — a list generated with guix import crate -r vacuum at release time. The Guix instructions therefore lead with the route that works today, guix shell -m manifest.scm -- cargo install --path crates/vacuum-cli.

Docs and CI

README and manual gain installation sections for Nix, NixOS, Guix System, Arch, and source — including a warning that cargo install vacuum fetches an unrelated crate of the same name (a spaceflight CLI). CI gains a nix flake check job that also smoke-tests the built binary.

Verification

nix build produces a working binary plus the Info manual; nix flake check passes; nix develop carries the full toolchain; the NixOS module was verified by evaluating it in a real nixosSystem, not by inspection.

Guix is not installed on this host, so manifest.scm and packaging/guix.scm are syntax-checked only — parsed with guile with the gexp reader extensions registered, matching a known-good sibling file structurally. Their package and module names have not been exercised against a real Guix.

Note the release path remains blocked until a v0.1.0 tag is cut and the real hashes filled in; that is deliberate and marked TODO(release).

🤖 Generated with Claude Code

https://claude.ai/code/session_01FCJbPm4FWS99y9utbUe13z

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.