the term was hard to discover, as its definition and explanation were in a very long document lacking an overview section. search did not help because it occurs so often. - clarify wording in the definition - add an overview of installable types - add "installable" to glossary - link to definition from occurrences of the term - be more precise about where store derivation outputs are processed - installable Nix expressions must evaluate to a derivation Co-authored-by: Adam Joseph <54836058+amjoseph-nixpkgs@users.noreply.github.com>
2.2 KiB
R""(
Examples
-
Show all packages in the
nixpkgs
flake:# nix search nixpkgs * legacyPackages.x86_64-linux.AMB-plugins (0.8.1) A set of ambisonics ladspa plugins * legacyPackages.x86_64-linux.ArchiSteamFarm (4.3.1.0) Application with primary purpose of idling Steam cards from multiple accounts simultaneously …
-
Show packages in the
nixpkgs
flake containingblender
in its name or description:# nix search nixpkgs blender * legacyPackages.x86_64-linux.blender (2.91.0) 3D Creation/Animation/Publishing System
-
Search for packages underneath the attribute
gnome3
in Nixpkgs:# nix search nixpkgs#gnome3 vala * legacyPackages.x86_64-linux.gnome3.vala (0.48.9) Compiler for GObject type system
-
Show all packages in the flake in the current directory:
# nix search
-
Search for Firefox or Chromium:
# nix search nixpkgs 'firefox|chromium'
-
Search for packages containing
git
and eitherfrontend
orgui
:# nix search nixpkgs git 'frontend|gui'
-
Search for packages containing
neovim
but hide ones containing eithergui
orpython
:# nix search nixpkgs neovim -e 'python|gui'
or
# nix search nixpkgs neovim -e 'python' -e 'gui'
Description
nix search
searches installable (which can be evaluated, that is, a
flake or Nix expression, but not a store path or store derivation path) for packages whose name or description matches all of the
regular expressions regex. For each matching package, It prints the
full attribute name (from the root of the installable), the version
and the meta.description
field, highlighting the substrings that
were matched by the regular expressions. If no regular expressions are
specified, all packages are shown.
Flake output attributes
If no flake output attribute is given, nix search
searches for
packages:
-
Directly underneath
packages.<system>
. -
Underneath
legacyPackages.<system>
, recursing into attribute sets that contain an attributerecurseForDerivations = true
.
)""