Jump to content

Nix (command): Difference between revisions

From NixOS Wiki
DoggoBit (talk | contribs)
m add navbox
Malix (talk | contribs)
No edit summary
 
Line 8: Line 8:
== Enabling the nix command ==
== Enabling the nix command ==


In nix 2.4 the nix command must be enabled explicitly set. You can do this in a few different ways.
In nix 2.4, the nix command must be explicitly enabled. You can do this in a few different ways.


For an individual invocation, eg.
=== As an individual invocation ===
<syntaxHighlight lang=text>
<syntaxhighlight lang="console">
nix --experimental-features nix-command build ...
nix --experimental-features nix-command build ...
</syntaxHighlight>
</syntaxhighlight>


Or by setting a user-specific configuration,
=== By setting it in the nix configuration ===
<syntaxHighlight lang=toml>
{{File|3=experimental-features = nix-command|name=~/.config/nix/nix.conf|lang=toml}}
# ~/.config/nix/nix.conf
experimental-features = nix-command
</syntaxHighlight>
in <code>~/.config/nix/nix.conf</code>.


On NixOS you can't edit <code>/etc/nix/nix.conf</code> directly, but you can enable this feature by editing <code>/etc/nixos/configuration.nix</code>:
=== On NixOS, by setting it in the NixOS configuration ===
<syntaxHighlight lang=nix>
''On NixOS you can't edit <code>/etc/nix/nix.conf</code> directly, so you have to set it through the NixOS configuration instead''
#
{{File|3={ pkgs, ... }: {
{ pkgs, ... }: {
  …
   nix.settings.experimental-features = [ "nix-command" ];
   nix.settings.experimental-features = [ "nix-command" ];
  …
}|name=/etc/nixos/configuration.nix|lang=nix}}{{Evaluate}}
}
</syntaxHighlight>
and then run <code>sudo nixos-rebuild switch</code> as always.


== Switching between <code>nix-env</code> and <code>nix profile</code> ==
== Switching from <code>nix profile</code> to <code>nix-env</code> ==
 
{{Warning|Using <code>nix-env</code> is not recommended.}}
{{warning|Be careful when testing.
Once you installed a package with <code>nix profile</code>, you get the following error message when using <code>nix-env</code>:
Once you have used <code>nix profile</code> you can no longer use <code>nix-env</code> without first deleting <code>/nix/var/nix/profiles/per-user/$USER/profile</code>}}
 
Once you installed a package with <code>nix profile</code>, you
get the following error message when using <code>nix-env</code>:


<syntaxHighlight lang=console>
<syntaxHighlight lang=console>
Line 47: Line 34:
</syntaxHighlight>
</syntaxHighlight>


To migrate back to <code>nix-env</code> you can delete your current profile:
To migrate from <code>nix profile</code> to <code>nix-env</code>, you need to delete your current profile:


{{warning|This will delete packages that have been installed before, so you may want to back this information before running the command.}}
{{warning|This will delete packages that have been installed before, so you may want to back this information before running the command.}}
Line 56: Line 43:


== New equivalents to old commands ==
== New equivalents to old commands ==
<syntaxHighlight lang=console>
<syntaxhighlight lang="shell">
# create a store derivation for a package defined in the current directory's default.nix
# create a store derivation for a package defined in the current directory's default.nix
old$ nix-instantiate -A somepackage
old$ nix-instantiate -A somepackage
Line 63: Line 50:
# alternative option
# alternative option
new$ nix derivation show .#somepackage | jq '.[keys[0]]' | nix derivation add
new$ nix derivation show .#somepackage | jq '.[keys[0]]' | nix derivation add
</syntaxHighlight>
</syntaxhighlight>


[[Category:Nix]]
[[Category:Nix]]

Latest revision as of 16:02, 7 September 2025

Introduction to Nix

Tools and applications

⤧︎
Disambiguation: This article is about the new nix command. Not to be confused with the Nix ecosystem, the Nix language or the Nix package manager.

This article is about the new nix command and all of its subcommands. The new nix command is intended to unify many different Nix package manager utilities that exist currently as many separate commands, eg. nix-build, nix-shell, etc.

See the Nix manual for a complete reference.

Enabling the nix command

In nix 2.4, the nix command must be explicitly enabled. You can do this in a few different ways.

As an individual invocation

nix --experimental-features nix-command build ...

By setting it in the nix configuration

≡︎ ~/.config/nix/nix.conf
experimental-features = nix-command

On NixOS, by setting it in the NixOS configuration

On NixOS you can't edit /etc/nix/nix.conf directly, so you have to set it through the NixOS configuration instead

❄︎ /etc/nixos/configuration.nix
{ pkgs, ... }: {
  nix.settings.experimental-features = [ "nix-command" ];
}
🟆︎
Tip: In order to affect your NixOS system by your nix-language-specific changes you must first evaluate it:
$ nixos-rebuild switch --sudo


Switching from nix profile to nix-env

⚠︎
Warning: Using nix-env is not recommended.

Once you installed a package with nix profile, you get the following error message when using nix-env:

$ nix-env -f '<nixpkgs>' -iA 'hello'
error: --- Error ----------------------------------------------------------------------------------------------------------------- nix-env
profile '/nix/var/nix/profiles/per-user/joerg/profile' is incompatible with 'nix-env'; please use 'nix profile' instead

To migrate from nix profile to nix-env, you need to delete your current profile:

⚠︎
Warning: This will delete packages that have been installed before, so you may want to back this information before running the command.
$ rm -rf /nix/var/nix/profiles/per-user/$USER/profile

New equivalents to old commands

# create a store derivation for a package defined in the current directory's default.nix
old$ nix-instantiate -A somepackage
# assumes you are now using flakes
new$ nix eval .#somepackage.drvPath
# alternative option
new$ nix derivation show .#somepackage | jq '.[keys[0]]' | nix derivation add