Flakes: Difference between revisions
Clarify when `nix flake init` can be used. |
m fix a few typos |
||
| Line 11: | Line 11: | ||
<!--T:184--> | <!--T:184--> | ||
Flakes also allow for locking references and versions, which can then be queried and updated | Flakes also allow for locking references and versions, which can then be queried and updated programmatically via the inputs {{cite manual|nix|command-ref/new-cli/nix3-flake-lock|number=7.5.19|title=nix flake lock}}{{cite manual|nix|command-ref/new-cli/nix3-flake-info|number=7.5.17|title=nix flake info}}. Additionally, an experimental CLI utility accepts flake references for expressions that build, run, and deploy packages.{{Cite manual|nix|command-ref/new-cli/nix|number=8.5.1|title=nix}} | ||
== Flake file structure == <!--T:185--> | == Flake file structure == <!--T:185--> | ||
| Line 135: | Line 135: | ||
<!--T:194--> | <!--T:194--> | ||
This flake produces a single flake output <code>packages</code>. And within that, <code>x86_64-linux</code> is a system- | This flake produces a single flake output <code>packages</code>. And within that, <code>x86_64-linux</code> is a system-specific attribute set. And within that, two package [[derivations]] <code>default</code> and <code>hello</code>. You can find outputs with the {{Nix Manual|name=show command|anchor=command-ref/new-cli/nix3-flake-show}} of a flake as shown below: | ||
</translate> | </translate> | ||