Every story and comment from the Hacker News API, in a layout borrowed from 2001.
A comment on Why did Nix introduce Flakes?. Parent comment
To explain what's happening:
- The example above is running `nix run <flake reference> -- <arguments to pass to the flake output's binary>`.
- The `<flake reference>` here is `.#cowsay`, which is to be read as: `<flake type>#<output from flake>`. The # is a separator here.
- The `<flake type>` being `.` implies its a local flake at the current directory. The `<output from flake` in this case is the `cowsay` program.
further fun to be found at: https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3...
As a meta-comment, yeah, this is kinda non-trivial for most of us. This is why we build devbox which provides a more familiar UX like `devbox add cowsay && devbox run -- cowsay "flakes are neat"`
There are no comments on this comment yet.
To explain what's happening:
- The example above is running `nix run <flake reference> -- <arguments to pass to the flake output's binary>`.
- The `<flake reference>` here is `.#cowsay`, which is to be read as: `<flake type>#<output from flake>`. The # is a separator here.
- The `<flake type>` being `.` implies its a local flake at the current directory. The `<output from flake` in this case is the `cowsay` program.
further fun to be found at: https://nixos.org/manual/nix/stable/command-ref/new-cli/nix3...
As a meta-comment, yeah, this is kinda non-trivial for most of us. This is why we build devbox which provides a more familiar UX like `devbox add cowsay && devbox run -- cowsay "flakes are neat"`