Cheatsheet: Difference between revisions

Line 40:

</syntaxHighlight>

Unfortunately, `nix-store` will try to load the entire file into memory,

Unfortunately, <code>nix-store</code> will try to load the entire file into memory,

which will fail if the file size exceeds available memory.

If we have root access, we can copy the file to the store ourselves:

Line 83:

=== Evaluate a NixOS configuration without building ===

If you only want to evaluate `configuration.nix` without building (e.g. to syntax-check or see if you are using module options correctly), you can use:

If you only want to evaluate <code>configuration.nix</code> without building (e.g. to syntax-check or see if you are using module options correctly), you can use:

Line 89:

</syntaxHighlight>

This creates the `.drv` file that `nixos-rebuild build` would build.

This creates the <code>.drv</code> file that <code>nixos-rebuild build</code> would build.

=== Manually switching a NixOS system to a certain version of system closure ===

Line 190:

</syntaxHighlight>

To initiate the build environment run `nix-shell` in the project root directory

To initiate the build environment run <code>nix-shell</code> in the project root directory

Line 210:

=== Evaluate packages for a different platform ===

Sometimes you want to check whether a change to a package (such as adding a new dependency) would evaluate even on a different type of system. For example, you may want to check on `x86_64-linux` whether a package evaluates for `x86_64-darwin` or `aarch64-linux`.

Sometimes you want to check whether a change to a package (such as adding a new dependency) would evaluate even on a different type of system. For example, you may want to check on <code>x86_64-linux</code> whether a package evaluates for <code>x86_64-darwin</code> or <code>aarch64-linux</code>.

Use the `system` argument:

Use the <code>system</code> argument:

Line 242:

</syntaxHighlight>

and the following in `configuration.nix`:

and the following in <code>configuration.nix</code>: