Emma ThorpeandClaude Opus 4.8
9b7a9fa9b9
CI / flake (pull_request) Successful in 13s
Record that any nixpkgs tool can be run on the fly via nix run / nix shell, so a missing command during development is not a dead end. Takes effect after a home-manager rebuild. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1012 B
1012 B
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| nix-shell-tooling | Any nixpkgs tool can be run ad hoc via nix run / nix shell — a missing command is never a dead end during development |
|
Any tool in nixpkgs can be run without installing it into the environment. If a command is missing during development, pull it from nixpkgs on the fly instead of working around its absence or reporting the tool as unavailable.
Why: Lyra runs NixOS; the ambient PATH is deliberately minimal, but the full nixpkgs set is always one command away. "command not found" is not a blocker.
How to apply:
- One-off run:
nix run nixpkgs#<pkg> -- <args>(e.g.nix run nixpkgs#jq -- .). - Tools on PATH for a session:
nix shell nixpkgs#<pkg> [nixpkgs#<pkg2> ...], then run commands normally. - Legacy form also works:
nix-shell -p <pkg> --run '<cmd>'. - Prefer this over hand-rolling a substitute for a tool that exists in nixpkgs.