Flakes: Difference between revisions
→Output schema: Link to the nix manual rather than the nix source so that links work (they did not in the github markdown page linked). |
m fix broken link |
||
| (One intermediate revision by one other user not shown) | |||
| Line 193: | Line 193: | ||
<!--T:103--> | <!--T:103--> | ||
Running <code>nix build</code> will look in the <code>legacyPackages</code> and <code>packages</code> output attributes for the corresponding [[derivation]] and then your system architecture and build the default output. If you want to specify a build attribute in a flake repository, you can run <code>nix build .#<attr></code>. In the example above, if you wanted to build the <code>packages.x86_64-linux.hello</code> attribute, run: | Running <code>nix build</code> will look in the <code>legacyPackages</code> and <code>packages</code> output attributes for the corresponding [[derivations|derivation]] and then your system architecture and build the default output. If you want to specify a build attribute in a flake repository, you can run <code>nix build .#<attr></code>. In the example above, if you wanted to build the <code>packages.x86_64-linux.hello</code> attribute, run: | ||
</translate> | </translate> | ||
| Line 381: | Line 381: | ||
<!--T:156--> | <!--T:156--> | ||
* <code>builtins.currentSystem</code> is non-hermetic and impure as it reflects the host system performing the | * <code>builtins.currentSystem</code> is non-hermetic and impure as it reflects the host system performing the evaluation. This can usually be avoided by passing the system (i.e., x86_64-linux) explicitly to derivations requiring it. | ||
<!--T:209--> | <!--T:209--> | ||