Translations:Flakes/103/en: Difference between revisions

Latest revision as of 15:37, 3 March 2026

Message definition (Flakes)

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:

Running nix build will look in the legacyPackages and packages 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 nix build .#<attr>. In the example above, if you wanted to build the packages.x86_64-linux.hello attribute, run:

Revision as of 09:45, 30 July 2024 view source FuzzyBot (talk \| contribs) 3,258 edits Importing a new version from external source Tags: Mobile edit Mobile web edit		Latest revision as of 15:37, 3 March 2026 view source FuzzyBot (talk \| contribs) 3,258 edits Importing a new version from external source
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	~~When in the repository top-level, run~~ <code>nix build ~~.#<attr>~~</code>~~. It~~ will look in the <code>legacyPackages</code> and <code>packages</code> output attributes for the corresponding derivation.		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: