Nixpkgs Reference Manual

Version 26.05.3869.95ca1e203c07


Table of Contents

Preface
Using Nixpkgs
Platform Support
Global configuration
Overlays
Overriding
Nixpkgs lib
Functions reference
Module System
Standard environment
The Standard Environment
Meta-attributes
Passthru-attributes
Multiple-output packages
Cross-compilation
Platform Notes
Toolchains
The LLVM Toolchain
Build helpers
Fixed-point arguments of build helpers
Fetchers
Trivial build helpers
Testers
Development Shell helpers
Special build helpers
Images
Hooks reference
Languages and frameworks
Packages
Modules
Generic
Development of Nixpkgs
Opening issues
Contributing to Nixpkgs
Quick Start to Adding a Package
Coding conventions
Submitting changes
Vulnerability Roundup
Reviewing contributions
Contributing to Nixpkgs documentation
Interoperability Standards
CycloneDX
A. Release Notes

List of Examples

1. Map over leaf attributes
2. Map over an leaf attributes defined by a condition
3. Create an interdependent package set on top of pkgs
4. Using callPackage from a scope
5. Enable debug symbols for use with GDB
6. Setting and accessing passthru attributes
7. Example definition of mkLocalDerivation extended from stdenv.mkDerivation with lib.extendMkDerivation
8. Update source hash with the fake hash method
9. Using fetchurl to download a file
10. Using fetchurl to download a file with multiple possible URLs
11. Manipulating the content downloaded by fetchurl
12. Using fetchzip to output contents directly
13. Using fetchzip to decompress a .rar file
14. Use sparseCheckout to only include some directories:
15. Invocation of runCommandWith
16. Invocation of runCommand
17. Usage 1 of makeDesktopItem
18. Usage 2 of makeDesktopItem
19. Usage 1 of writeTextFile
20. Usage 2 of writeTextFile
21. Usage 3 of writeTextFile
22. Usage of writeText
23. Usage of writeTextDir
24. Usage of writeScript
25. Usage of writeScriptBin
26. Usage of writeShellScript
27. Usage of writeShellScriptBin
28. Usage of writeShellApplication
29. Check that pkg-config modules are exposed using default values
30. Check that pkg-config modules are exposed using explicit module names
31. Check that *config.cmake modules are exposed using explicit module names
32. Check hyperlinks in the nix documentation
33. Run testers.shellcheck
34. Run testers.shfmt
35. Check a program version using all the default values
36. Check the program version using a specified command and expected version string
37. Check that a build fails, and verify the changes made during build
38. Check that a build fails, and verify the changes made during build
39. Check that two paths have the same contents
40. Test a function which appends a value to an array
41. Check that two packages produce the same derivation
42. Prevent nix from reusing the output of a fetcher
43. Run a command with network access
44. Run a NixOS test using runNixOSTest
45. Using fakeNss with dockerTools.buildImage
46. Using fakeNss with an override to add extra lines
47. Wrapping an AppImage from GitHub
48. Wrapping an AppImage with extra packages
49. Extracting an AppImage to install extra files
50. Extracting an AppImage to install extra files, using postExtract
51. Building a Docker image
52. Building a Docker image with runAsRoot
53. Building a Docker image with extraCommands
54. Building a Docker image with a creation date set to the current time
55. Building a layered Docker image
56. Streaming a layered Docker image
57. Exploring the layers in an image built with streamLayeredImage
58. Building a layered Docker image with packages directly in config
59. Pulling the nixos/nix Docker image from the default registry
60. Pulling the nixos/nix Docker image from a specific registry
61. Finding the digest and hash values to use for dockerTools.pullImage
62. Exporting a Docker image with dockerTools.exportImage
63. Importing an archive built with dockerTools.exportImage in Docker
64. Exploring output naming with dockerTools.exportImage
65. Using dockerTools.exportImage with a path as fromImage
66. Using dockerTools’s environment helpers with buildImage
67. Using dockerTools’s environment helpers with buildLayeredImage
68. Using dockerTools.shadowSetup with dockerTools.buildImage
69. Using dockerTools.shadowSetup with dockerTools.buildLayeredImage
70. Building a Docker image with buildNixShellImage with the build environment for the hello package
71. Building a Docker image with streamNixShellImage with the build environment for the hello package
72. Adding extra packages to a Docker image built with streamNixShellImage
73. Adding a shellHook to a Docker image built with streamNixShellImage
74. Creating an OCI runtime container that runs bash
75. Building a Portable Service image
76. Specifying symlinks when building a Portable Service image
77. Copying a package and its closure to another machine with mkBinaryCache
78. Using npmHooks
79. Navigate Java compiler variants in javaPackages with nix repl
80. List all Python packages in Nixpkgs
81. Ephemeral shell
82. Declarative shell
83. Using pkgs.zlib.override {}
84. Using pkgs.buildEmscriptenPackage {}
85. Overriding the kernel derivation
86. Using pkgs.linuxPackages_custom with a specific source, version, and config file
87. Edit-compile-run loop when developing mellanox drivers
88. Usage of pkgs.substitute
89. Usage of pkgs.replaceVars
90. Usage of pkgs.replaceVarsWith

Preface

Table of Contents

Overview of Nixpkgs

The Nix Packages collection (Nixpkgs) is a set of thousands of packages for the Nix package manager, released under a permissive MIT license. Packages are available for several platforms, and can be used with the Nix package manager on most GNU/Linux distributions as well as NixOS.

This document is the user reference manual for Nixpkgs. It describes the entire public interface of Nixpkgs in a concise and orderly manner, and all relevant behaviors, with examples and cross-references.

To discover other kinds of documentation:

Overview of Nixpkgs

Nix expressions describe how to build packages from source and are collected in the Nixpkgs repository. Also included in the collection are Nix expressions for NixOS modules. With these expressions the Nix package manager can build binary packages.

Packages, including the Nix packages collection, are distributed through channels. The collection is distributed for users of Nix on non-NixOS distributions through the channel nixpkgs-unstable. Users of NixOS generally use one of the nixos-* channels, e.g., nixos-22.11, which includes all packages and modules for the stable NixOS 22.11. Stable NixOS releases are generally only given security updates. More up-to-date packages and modules are available via the nixos-unstable channel.

Both nixos-unstable and nixpkgs-unstable follow the master branch of the Nixpkgs repository, although both do lag the master branch by generally a couple of days. Updates to a channel are distributed as soon as all tests for that channel pass, e.g., this table shows the status of tests for the nixpkgs-unstable channel.

The tests are conducted by a cluster called Hydra, which also builds binary packages from the Nix expressions in Nixpkgs for x86_64-linux, aarch64-linux, x86_64-darwin and aarch64-darwin. The binaries are made available via a binary cache.

The current Nix expressions of the channels are available in the Nixpkgs repository in branches that correspond to the channel names (e.g., nixos-22.11-small).

Using Nixpkgs

Platform Support

Table of Contents

Tiers
Breakdown

Packages receive varying degrees of support, both in terms of maintainer attention and available computation resources for continuous integration (CI). We have 7 defined tiers denoting how well supported each platform is.

Tiers

Tier 1

Tier 1 platforms receive the highest level of support where problems can block updates, platform-specific patches are freely applied, and most packages are expected to work.

Tier 2

Tier 2 platforms are expected to remain functional with updates, receive platform-specific patches as needed, and have many packages built by Hydra with full ofBorg support.

Tier 3

Tier 3 platforms may receive non-intrusive platform-specific fixes, have native bootstrap tools available with cross-build toolchains in binary cache, but updates might break builds on these platforms.

Tier 4-7

Platform Tiers 4 through 7 indicate varying levels of minimal support going from receiving only limited fixes to platforms with no support, but a path to support.

Breakdown

TripleSupport TierChannel BlockersHydra SupportOfborg SupportBootstrap TarballsCross Compiling Support
x86_64-unknown-linux-gnuTier 1Many✔️✔️✔️✔️
aarch64-unknown-linux-gnuTier 2Some✔️✔️✔️✔️
x86_64-unknown-linux-muslTier 3NoneLimited✔️✔️
aarch64-unknown-linux-muslTier 3NoneLimited✔️✔️
x86_64-unknown-unknown-freebsdTier 3None✔️✔️
arm64-apple-darwinTier 2Some✔️✔️✔️❌*
x86_64-apple-darwinTier 2Some✔️✔️✔️❌*
i686-unknown-linux-gnuTier 3NoneLimited✔️✔️
riscv32-unknown-linux-gnuTier 4None✔️
riscv64-unknown-linux-gnuTier 3None✔️✔️
loongarch64-unknown-linux-gnuTier 3None✔️✔️
armv6l-unknown-linux-gnueabihfTier 3None✔️✔️
armv6l-unknown-linux-musleabihfTier 3None✔️✔️
armv7l-unknown-linux-gnueabihfTier 3None✔️✔️
armv5tel-unknown-linux-gnueabiTier 3None✔️✔️
mips64el-unknown-linux-gnuabi64Tier 3None✔️✔️
mips64el-unknown-linux-gnuabin32Tier 3None✔️✔️
mipsel-unknown-linux-gnuTier 3None✔️✔️
powerpc64-unknown-linux-gnuabielfv2Tier 3None✔️✔️
powerpc64le-unknown-linux-gnuTier 3None✔️✔️
s390x-unknown-linux-gnuTier 3None✔️✔️

* - Cross compiling is only supported on Darwin hosts.

Global configuration

Nix comes with certain defaults about which packages can and cannot be installed, based on a package’s metadata. By default, Nix will prevent installation if any of the following criteria are true:

  • The package is thought to be broken, and has had its meta.broken set to true.

  • The package isn’t intended to run on the given system, as none of its meta.platforms match the given system.

  • The package’s meta.license is set to a license which is considered to be unfree.

  • The package has known security vulnerabilities but has not or can not be updated for some reason, and a list of issues has been entered into the package’s meta.knownVulnerabilities.

  • There are problems for packages which must be acknowledged, e.g. deprecation notices.

Each of these criteria can be altered in the Nixpkgs configuration.

Note

All this is checked during evaluation already, and the check includes any package that is evaluated. In particular, all build-time dependencies are checked.

A user’s Nixpkgs configuration is stored in a user-specific configuration file located at ~/.config/nixpkgs/config.nix. For example:

{ allowUnfree = true; }

Caution

Unfree software is not tested or built in Nixpkgs continuous integration, and therefore not cached. Most unfree licenses prohibit either executing or distributing the software.

The NIXPKGS_CONFIG environment variable can override the configuration file location. Nixpkgs resolves the config in this order:

  1. $NIXPKGS_CONFIG, if set and the file exists.

  2. ~/.config/nixpkgs/config.nix, if it exists.

  3. ~/.nixpkgs/config.nix (legacy), if it exists.

  4. Empty configuration.

On NixOS, NIXPKGS_CONFIG points to /etc/nix/nixpkgs-config.nix system-wide. Drop a file there to apply configuration to nix-env, nix-shell, and other user-level commands. NixOS does not create this file. The nixpkgs.config option does not affect nix-env, nix-shell, or other user-level commands.

This lookup applies to non-flake usage like channels and <nixpkgs>. Flakes ignore it; pass config directly when importing nixpkgs.

Installing broken packages

There are several ways to try compiling a package which has been marked as broken.

  • For allowing the build of a broken package once, you can use an environment variable for a single invocation of the nix tools:

    $ export NIXPKGS_ALLOW_BROKEN=1
    
  • For permanently allowing broken packages with a specific name to be built, you may add a corresponding problems.handlers to your user’s configuration file, for example:

    {
      problems.handlers.hello.broken = "warn"; # or "ignore"
    }
    
  • For permanently allowing all broken packages to be built, you may add allowBroken = true; to your user’s configuration file, like this:

    { allowBroken = true; }
    

Installing packages on unsupported systems

There are also two ways to try compiling a package which has been marked as unsupported for the given system.

  • For allowing the build of an unsupported package once, you can use an environment variable for a single invocation of the nix tools:

    $ export NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM=1
    
  • For permanently allowing unsupported packages to be built, you may add allowUnsupportedSystem = true; to your user’s configuration file, like this:

    { allowUnsupportedSystem = true; }
    

The difference between a package being unsupported on some system and being broken is admittedly a bit fuzzy. If a program ought to work on a certain platform, but doesn’t, the platform should be included in meta.platforms, but marked as broken with e.g. meta.broken = !hostPlatform.isWindows. Of course, this begs the question of what “ought” means exactly. That is left to the package maintainer.

Installing unfree packages

All users of Nixpkgs are free software users, and many users (and developers) of Nixpkgs want to limit and tightly control their exposure to unfree software. At the same time, many users need (or want) to run some specific pieces of proprietary software. Nixpkgs includes some expressions for unfree software packages. By default unfree software cannot be installed and doesn’t show up in searches.

There are several ways to tweak how Nix handles a package which has been marked as unfree.

  • To temporarily allow all unfree packages, you can use an environment variable for a single invocation of the nix tools:

    $ export NIXPKGS_ALLOW_UNFREE=1
    
  • It is possible to permanently allow individual unfree packages, while still blocking unfree packages by default using the allowUnfreePredicate configuration option in the user configuration file.

    This option is a function which accepts a package as a parameter, and returns a boolean. The following example configuration accepts a package and always returns false:

    { allowUnfreePredicate = (pkg: false); }
    

    For a more useful example, try the following. This configuration only allows unfree packages named roon-server and Visual Studio Code:

    {
      allowUnfreePredicate =
        pkg:
        builtins.elem (lib.getName pkg) [
          "roon-server"
          "vscode"
        ];
    }
    
  • It is also possible to allow and block licenses that are specifically acceptable or not acceptable, using allowlistedLicenses and blocklistedLicenses, respectively.

    The following example configuration allowlists the licenses amd and wtfpl:

    {
      allowlistedLicenses = with lib.licenses; [
        amd
        wtfpl
      ];
    }
    

    The following example configuration blocklists the gpl3Only and agpl3Only licenses:

    {
      blocklistedLicenses = with lib.licenses; [
        agpl3Only
        gpl3Only
      ];
    }
    

    Note that allowlistedLicenses only applies to unfree licenses unless allowUnfree is enabled. It is not a generic allowlist for all types of licenses. blocklistedLicenses applies to all licenses.

A complete list of licenses can be found in the file lib/licenses.nix of the nixpkgs tree.

Installing insecure packages

There are several ways to tweak how Nix handles a package which has been marked as insecure.

  • To temporarily allow all insecure packages, you can use an environment variable for a single invocation of the nix tools:

    $ export NIXPKGS_ALLOW_INSECURE=1
    
  • It is possible to permanently allow individual insecure packages, while still blocking other insecure packages by default using the permittedInsecurePackages configuration option in the user configuration file.

    The following example configuration permits the installation of the hypothetically insecure package hello, version 1.2.3:

    { permittedInsecurePackages = [ "hello-1.2.3" ]; }
    
  • It is also possible to create a custom policy around which insecure packages to allow and deny, by overriding the allowInsecurePredicate configuration option.

    The allowInsecurePredicate option is a function which accepts a package and returns a boolean, much like allowUnfreePredicate.

    The following configuration example allows any version of the ovftool package:

    { allowInsecurePredicate = pkg: builtins.elem (lib.getName pkg) [ "ovftool" ]; }
    

    Note that permittedInsecurePackages is only checked if allowInsecurePredicate is not specified.

Packages with problems

A package may have several problems associated with it. These can be either manually declared in meta.problems, or automatically generated from its other meta attributes. Each problem has a name, a “kind”, a message, and optionally a list of URLs. Not all kinds can be manually specified in meta.problems, and some kinds can exist only up to once per package. Currently, the following problem kinds are known (with more reserved to be added in the future):

  • “removal”: The package is planned to be removed some time in the future. Unique.

  • “deprecated”: The package relies on software which has reached its end of life.

  • “maintainerless”: Automatically generated for packages with meta.maintainers == []. Unique, not manually specifiable.

  • “broken”: Automatically generated for packages with meta.broken = true.

Each problem has a handler that deals with it, which can be one of “error”, “warn” or “ignore”. “error” will disallow evaluating a package, while “warn” will simply print a message to the log.

The handler for problems can be specified using config.problems.handlers.${packageName}.${problemName} = "${handler}";.

There is also the possibility to specify some generic matchers, which can set a handler for more than a specific problem of a specific package. This works through the config.problems.matchers option:

{
  problems.matchers = [
    # Fail to build any packages which are about to be removed anyway
    {
      kind = "removal";
      handler = "error";
    }

    # Get warnings when using packages with no declared maintainers
    {
      kind = "maintainerless";
      handler = "warn";
    }

    # You deeply care about this package and want to absolutely know when it has any problems
    {
      package = "hello";
      handler = "error";
    }
  ];
}

Matchers can match one or more of package name, problem name or problem kind. If multiple conditions are present, all must be met to match. If multiple matchers match a problem, then the highest severity handler will be chosen. The current default value contains { kind = "removal"; handler = "warn"; }, meaning that people will be notified about package removals in advance.

Package names for both problems.handlers and problems.matchers are taken from lib.getName, which looks at the pname first and falls back to extracting the “pname” part from the name attribute.

Modify packages via packageOverrides

You can define a function called packageOverrides in your local ~/.config/nixpkgs/config.nix to override Nix packages. It must be a function that takes pkgs as an argument and returns a modified set of packages.

{
  packageOverrides = pkgs: rec {
    foo = pkgs.foo.override {
      # ...
    };
  };
}

config Options Reference

The following attributes can be passed in config.

enableParallelBuildingByDefault

Whether to set enableParallelBuilding to true by default while building nixpkgs packages. Changing the default may cause a mass rebuild.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
allowAliases

Whether to expose old attribute names for compatibility.

The recommended setting is to enable this, as it improves backward compatibility, easing updates.

The only reason to disable aliases is for continuous integration purposes. For instance, Nixpkgs should not depend on aliases in its internal code. Projects that aren’t Nixpkgs should be cautious of instantly removing all usages of aliases, as migrating too soon can break compatibility with the stable Nixpkgs releases.

Type: boolean

Default:

true

Declared by:

pkgs/top-level/config.nix
allowBroken

Whether to allow broken packages.

See Installing broken packages in the NixOS manual.

Type: boolean

Default:

false || builtins.getEnv "NIXPKGS_ALLOW_BROKEN" == "1"

Declared by:

pkgs/top-level/config.nix
allowDeprecatedx86_64Darwin

Silence the warning for the upcoming deprecation of the x86_64-darwin platform in Nixpkgs 26.11.

See the release notes for more information.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
allowUnfree

Whether to allow unfree packages.

See Installing unfree packages in the NixOS manual.

Type: boolean

Default:

false || builtins.getEnv "NIXPKGS_ALLOW_UNFREE" == "1"

Declared by:

pkgs/top-level/config.nix
allowUnfreePackages

Allows specific unfree packages to be used.

This option composes with nixpkgs.config.allowUnfreePredicate by also allowing the listed package names.

Unlike nixpkgs.config.allowUnfreePredicate, this option merges additively, similar to environment.systemPackages. This enables defining allowed unfree packages in multiple modules, close to where they are used.

This avoids the need to centralize all unfree package declarations or globally enable unfree packages via nixpkgs.config.allowUnfree = true.

Type: list of string

Default:

[ ]

Example:

[
  "ut1999"
]

Declared by:

pkgs/top-level/config.nix
allowUnsupportedSystem

Whether to allow unsupported packages.

See Installing packages on unsupported systems in the NixOS manual.

Type: boolean

Default:

false || builtins.getEnv "NIXPKGS_ALLOW_UNSUPPORTED_SYSTEM" == "1"

Declared by:

pkgs/top-level/config.nix
allowVariants

Whether to expose the nixpkgs variants.

Variants are instances of the current nixpkgs instance with different stdenvs or other applied options. This allows for using different toolchains, libcs, or global build changes across nixpkgs. Disabling can ensure nixpkgs is only building for the platform which you specified.

Type: boolean

Default:

true

Declared by:

pkgs/top-level/config.nix
attrPathsDisallowedForInternalUse.*.attrPath

Attribute path to disallow.

Type: list of string

Default:

[ ]

Declared by:

pkgs/top-level/config.nix
attrPathsDisallowedForInternalUse.*.reason

Reason for it being disallowed.

Type: null or string

Default:

null

Example:

"it's dangerous."

Declared by:

pkgs/top-level/config.nix
checkMeta

Whether to check that the meta attribute of derivations are correct during evaluation time.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
configurePlatformsByDefault

Whether to set configurePlatforms to ["build" "host"] by default while building nixpkgs packages. Changing the default may cause a mass rebuild.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
contentAddressedByDefault

Whether to set __contentAddressed to true by default while building nixpkgs packages. Changing the default may cause a mass rebuild.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
cudaCapabilities

A list of CUDA capabilities to build for.

Packages may use this option to control device code generation to take advantage of architecture-specific functionality, speed up compile times by producing less device code, or slim package closures.

For example, you can build for Ada Lovelace GPUs with cudaCapabilities = [ "8.9" ];.

If not provided, the default value is calculated per-package set, derived from a list of GPUs supported by that CUDA version.

See the CUDA section in the Nixpkgs manual for more information.

Type: list of string

Default:

[ ]

Declared by:

pkgs/top-level/config.nix
cudaForwardCompat

Whether to enable PTX support for future hardware.

When enabled, packages will include PTX code that can be JIT-compiled for GPUs newer than those explicitly targeted by cudaCapabilities.

Type: boolean

Default:

true

Declared by:

pkgs/top-level/config.nix
cudaSupport

Whether to build packages with CUDA support by default while building nixpkgs packages. Changing the default may cause a mass rebuild.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
doCheckByDefault

Whether to run checkPhase by default while building nixpkgs packages. Changing the default may cause a mass rebuild.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
fetchedSourceNameDefault

This controls the default derivation name attribute set by the fetch* (fetchzip, fetchFromGitHub, etc) functions.

Possible values and the resulting .name:

  • "source" -> "source"

  • "versioned" -> "${repo}-${rev}-source"

  • "full" -> "${repo}-${rev}-${fetcherName}-source"

The default "source" is the best choice for minimal rebuilds, it will ignore any non-hash changes (like branches being renamed, source URLs changing, etc) at the cost of /nix/store being easily cache-poisoned (see NixOS/nix#969).

Setting this to "versioned" greatly helps with discoverability of sources in /nix/store and makes cache-poisoning of /nix/store much harder, at the cost of a single mass-rebuild for all src derivations, and an occasional rebuild when a source changes some of its non-hash attributes.

Setting this to "full" is similar to setting it to "versioned", but the use of fetcherName in the derivation name will force a rebuild when src switches between fetch* functions, thus forcing nix to check new derivation’s outputHash, which is useful for debugging.

Also, "full" is useful for easy collection and tracking of statistics of where the packages you use are hosted.

If you are a developer, you should probably set this to at least"versioned".

Changing the default will cause a mass rebuild.

Type: one of “source”, “versioned”, “full”

Default:

"source"

Declared by:

pkgs/top-level/config.nix
gitConfig

The default git configuration for all pkgs.fetchgit calls.

Among many other potential uses, this can be used to override URLs to point to local mirrors.

Changing this will not cause any rebuilds because pkgs.fetchgit produces a fixed-output derivation.

To set the configuration file directly, use the gitConfigFile option instead.

To set the configuration file for individual calls, use fetchgit { gitConfigFile = "..."; }.

Type: attribute set of attribute set of anything

Default:

{ }

Example:

{
  url = {
    "https://my-github-mirror.local" = {
      insteadOf = [
        "https://github.com"
      ];
    };
  };
}

Declared by:

pkgs/top-level/config.nix
gitConfigFile

A path to a git configuration file, to be used for all pkgs.fetchgit calls.

This overrides the gitConfig option, see its documentation for more details.

Type: null or absolute path

Default:

null

Declared by:

pkgs/top-level/config.nix
hashedMirrors

The set of content-addressed/hashed mirror URLs used by pkgs.fetchurl. In case pkgs.fetchurl can’t download from the given URLs, it will try the hashed mirrors based on the expected output hash.

See copy-tarballs.pl for more details on how hashed mirrors are constructed.

Type: list of string

Default:

[
  "https://tarballs.nixos.org"
]

Declared by:

pkgs/top-level/config.nix
microsoftVisualStudioLicenseAccepted

If the Microsoft Visual Studio license has been accepted.

Please read https://www.visualstudio.com/license-terms/mt644918/ and enable this config if you accept.

Type: boolean

Default:

false || builtins.getEnv "NIXPKGS_ALLOW_UNFREE" == "1"

Declared by:

pkgs/top-level/config.nix
npmRegistryOverrides

The default npm registry overrides for all fetchNpmDeps calls, as an attribute set.

For each attribute, all files fetched from the host corresponding to the name will instead be fetched from the host (and sub-path) specified in the value.

For example, an override like "registry.npmjs.org" = "my-mirror.local/registry.npmjs.org" will replace a URL like https://registry.npmjs.org/foo.tar.gz with https://my-mirror.local/registry.npmjs.org/foo.tar.gz.

To set the string directly, see npmRegistryOverridesString.

Type: attribute set of string

Default:

{ }

Example:

{
  "registry.npmjs.org" = "my-mirror.local/registry.npmjs.org";
}

Declared by:

pkgs/top-level/config.nix
npmRegistryOverridesString

A string containing a string with a JSON representation of npm registry overrides for fetchNpmDeps.

This overrides the npmRegistryOverrides option, see its documentation for more details.

Type: string

Default:

"{}"

Declared by:

pkgs/top-level/config.nix
problems.handlers

Specify how to handle packages with problems. Each key has the format packageName.problemName, each value is one of “error”, “warn” or “ignore”.

This option takes precedence over anything in problems.matchers.

Package names are taken from lib.getName, which looks at the pname first and falls back to extracting the “pname” part from the name attribute.

See <link xlink:href=“https://nixos.org/manual/nixpkgs/stable/#sec-ignore-problems”>Installing packages with problems</link> in the NixOS manual.

Type: attribute set of attribute set of (one of “ignore”, “warn”, “error”)

Default:

{ }

Declared by:

pkgs/top-level/config.nix
problems.matchers

A more powerful and less ergonomic version of problems.handlers. Each value is a matcher, that may match onto certain properties of a problem and specify a handler for them.

If multiple matchers match a problem, the handler with the highest severity (error > warn > ignore) will be used. Values in problems.handlers always take precedence over matchers.

Any matchers must not contain both a package and name field, for this should be handled by using problems.handlers instead.

Type: list of (submodule)

Default:

[ ]

Example:

[
  {
    handler = "warn";
    kind = "maintainerless";
  }
  {
    handler = "error";
    package = "myPackageICareAbout";
  }
]

Declared by:

pkgs/top-level/config.nix
problems.matchers.*.package

Match problems of packages with this name

Type: null or string

Default:

null

Declared by:

pkgs/top-level/config.nix
problems.matchers.*.handler

Specify the handler for matched problems

Type: one of “ignore”, “warn”, “error”

Declared by:

pkgs/top-level/config.nix
problems.matchers.*.kind

Match problems of this problem kind

Type: null or one of “broken”, “deprecated”, “maintainerless”, “removal”

Default:

null

Declared by:

pkgs/top-level/config.nix
problems.matchers.*.name

Match problems with this problem name

Type: null or string

Default:

null

Declared by:

pkgs/top-level/config.nix
recursionMode

In which way to recurse through Nixpkgs. In most cases you want keep this as the default. You can use this to emulate how hydra and search are going through Nixpkgs.

Type: one of “hydra”, “eval”, “search”

Default:

"eval"

Declared by:

pkgs/top-level/config.nix
replaceBootstrapFiles

Use the bootstrap files returned instead of the default bootstrap files. The default bootstrap files are passed as an argument. Changing the default may cause a mass rebuild.

Type: function that evaluates to a(n) attribute set of package

Default:

lib.id

Example:

prevFiles:
let
  replacements = {
    "sha256-YQlr088HPoVWBU2jpPhpIMyOyoEDZYDw1y60SGGbUM0=" = import <nix/fetchurl.nix> {
      url = "(custom glibc linux x86_64 bootstrap-tools.tar.xz)";
      hash = "(...)";
    };
    "sha256-QrTEnQTBM1Y/qV9odq8irZkQSD9uOMbs2Q5NgCvKCNQ=" = import <nix/fetchurl.nix> {
      url = "(custom glibc linux x86_64 busybox)";
      hash = "(...)";
      executable = true;
    };
  };
in
builtins.mapAttrs (name: prev: replacements.${prev.outputHash} or prev) prevFiles

Declared by:

pkgs/top-level/config.nix
replaceStdenv

A function to replace the standard environment (stdenv).

The function receives an attribute set with pkgs and should return a stdenv derivation.

This can be used to globally replace the stdenv with a custom one, for example to use ccache or distcc. Changing the default may cause a mass rebuild.

Type: null or (function that evaluates to a(n) package)

Default:

null

Example:

{ pkgs }: pkgs.ccacheStdenv

Declared by:

pkgs/top-level/config.nix
rewriteURL

A hook to rewrite/filter URLs before they are fetched.

The function is passed the URL as a string, and is expected to return a new URL, or null if the given URL should not be attempted.

This function is applied prior to resolving mirror:// URLs.

The intended use is to allow URL rewriting to insert company-internal mirrors, or work around company firewalls and similar network restrictions.

Type: function that evaluates to a(n) (null or string)

Default:

(url: url)

Example:

{
  # Use Nix like it's 2024! ;-)
  rewriteURL = url: "https://web.archive.org/web/2024/${url}";
}

Declared by:

pkgs/top-level/config.nix
rocmSupport

Whether to build packages with ROCm support by default while building nixpkgs packages. Changing the default may cause a mass rebuild.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
showDerivationWarnings

Which warnings to display for potentially dangerous or deprecated values passed into stdenv.mkDerivation.

A list of warnings can be found in /pkgs/stdenv/generic/check-meta.nix.

This is not a stable interface; warnings may be added, changed or removed without prior notice.

Type: list of value “maintainerless” (singular enum)

Default:

[ ]

Declared by:

pkgs/top-level/config.nix
strictDepsByDefault

Whether to set strictDeps to true by default while building nixpkgs packages. Changing the default may cause a mass rebuild.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
structuredAttrsByDefault

Whether to set __structuredAttrs to true by default while building nixpkgs packages. Changing the default may cause a mass rebuild.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix
warnUndeclaredOptions

Whether to warn when config contains an unrecognized attribute.

Type: boolean

Default:

false

Declared by:

pkgs/top-level/config.nix

Declarative Package Management

Build an environment

Using packageOverrides, it is possible to manage packages declaratively. This means that we can list all of our desired packages within a declarative Nix expression. For example, to have aspell, bc, ffmpeg, coreutils, gdb, nix, emscripten, jq, nox, and silver-searcher, we could use the following in ~/.config/nixpkgs/config.nix:

{
  packageOverrides =
    pkgs: with pkgs; {
      myPackages = pkgs.buildEnv {
        name = "my-packages";
        paths = [
          aspell
          bc
          coreutils
          gdb
          ffmpeg
          nix
          emscripten
          jq
          nox
          silver-searcher
        ];
      };
    };
}

To install it into our environment, you can just run nix-env -iA nixpkgs.myPackages. If you want to load the packages to be built from a working copy of nixpkgs you just run nix-env -f. -iA myPackages. To explore what’s been installed, just look through ~/.nix-profile/. You can see that a lot of stuff has been installed. Some of this stuff is useful some of it isn’t. Let’s tell Nixpkgs to only link the stuff that we want:

{
  packageOverrides =
    pkgs: with pkgs; {
      myPackages = pkgs.buildEnv {
        name = "my-packages";
        paths = [
          aspell
          bc
          coreutils
          gdb
          ffmpeg
          nix
          emscripten
          jq
          nox
          silver-searcher
        ];
        pathsToLink = [
          "/share"
          "/bin"
        ];
      };
    };
}

pathsToLink tells Nixpkgs to only link the paths listed which gets rid of the extra stuff in the profile. /bin and /share are good defaults for a user environment, getting rid of the clutter. If you are running on Nix on macOS, you may want to add another path as well, /Applications, that makes GUI apps available.

Getting documentation

After building that new environment, look through ~/.nix-profile to make sure everything is there that we wanted. Discerning readers will note that some files are missing. Look inside ~/.nix-profile/share/man/man1/ to verify this. There are no man pages for any of the Nix tools! This is because some packages like Nix have multiple outputs for things like documentation (see section 4). Let’s make Nix install those as well.

{
  packageOverrides =
    pkgs: with pkgs; {
      myPackages = pkgs.buildEnv {
        name = "my-packages";
        paths = [
          aspell
          bc
          coreutils
          ffmpeg
          nix
          emscripten
          jq
          nox
          silver-searcher
        ];
        pathsToLink = [
          "/share/man"
          "/share/doc"
          "/bin"
        ];
        extraOutputsToInstall = [
          "man"
          "doc"
        ];
      };
    };
}

This provides us with some useful documentation for using our packages. However, if we actually want those manpages to be detected by man, we need to set up our environment. This can also be managed within Nix expressions.

{
  packageOverrides = pkgs: {
    myProfile = pkgs.writeText "my-profile" ''
      export PATH=$HOME/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/sbin:/bin:/usr/sbin:/usr/bin
      export MANPATH=$HOME/.nix-profile/share/man:/nix/var/nix/profiles/default/share/man:/usr/share/man
    '';
    myPackages = pkgs.buildEnv {
      name = "my-packages";
      paths = with pkgs; [
        (runCommand "profile" { } ''
          mkdir -p $out/etc/profile.d
          cp ${myProfile} $out/etc/profile.d/my-profile.sh
        '')
        aspell
        bc
        coreutils
        ffmpeg
        man
        nix
        emscripten
        jq
        nox
        silver-searcher
      ];
      pathsToLink = [
        "/share/man"
        "/share/doc"
        "/bin"
        "/etc"
      ];
      extraOutputsToInstall = [
        "man"
        "doc"
      ];
    };
  };
}

For this to work fully, you must also have this script sourced when you are logged in. Try adding something like this to your ~/.profile file:

#!/bin/sh
if [ -d "${HOME}/.nix-profile/etc/profile.d" ]; then
  for i in "${HOME}/.nix-profile/etc/profile.d/"*.sh; do
    if [ -r "$i" ]; then
      . "$i"
    fi
  done
fi

Now just run . "${HOME}/.profile" and you can start loading man pages from your environment.

GNU info setup

Configuring GNU info is a little bit trickier than man pages. To work correctly, info needs a database to be generated. This can be done with some small modifications to our environment scripts.

{
  packageOverrides = pkgs: {
    myProfile = pkgs.writeText "my-profile" ''
      export PATH=$HOME/.nix-profile/bin:/nix/var/nix/profiles/default/bin:/sbin:/bin:/usr/sbin:/usr/bin
      export MANPATH=$HOME/.nix-profile/share/man:/nix/var/nix/profiles/default/share/man:/usr/share/man
      export INFOPATH=$HOME/.nix-profile/share/info:/nix/var/nix/profiles/default/share/info:/usr/share/info
    '';
    myPackages = pkgs.buildEnv {
      name = "my-packages";
      paths = with pkgs; [
        (runCommand "profile" { } ''
          mkdir -p $out/etc/profile.d
          cp ${myProfile} $out/etc/profile.d/my-profile.sh
        '')
        aspell
        bc
        coreutils
        ffmpeg
        man
        nix
        emscripten
        jq
        nox
        silver-searcher
        texinfoInteractive
      ];
      pathsToLink = [
        "/share/man"
        "/share/doc"
        "/share/info"
        "/bin"
        "/etc"
      ];
      extraOutputsToInstall = [
        "man"
        "doc"
        "info"
      ];
      postBuild = ''
        if [ -x $out/bin/install-info -a -w $out/share/info ]; then
          shopt -s nullglob
          for i in $out/share/info/*.info $out/share/info/*.info.gz; do
              $out/bin/install-info $i $out/share/info/dir
          done
        fi
      '';
    };
  };
}

postBuild tells Nixpkgs to run a command after building the environment. In this case, install-info adds the installed info pages to dir which is GNU info’s default root node. Note that texinfoInteractive is added to the environment to give the install-info command.

Overlays

This chapter describes how to extend and change Nixpkgs using overlays. Overlays are used to add layers in the fixed-point used by Nixpkgs to compose the set of all packages.

Nixpkgs can be configured with a list of overlays, which are applied in order. This means that the order of the overlays can be significant if multiple layers override the same package.

Installing overlays

The list of overlays can be set either explicitly in a Nix expression, or through <nixpkgs-overlays> or user configuration files.

Set overlays in NixOS or Nix expressions

On a NixOS system the value of the nixpkgs.overlays option, if present, is passed to the system Nixpkgs directly as an argument. Note that this does not affect the overlays for non-NixOS operations (e.g. nix-env), which are looked up independently.

The list of overlays can be passed explicitly when importing nixpkgs, for example import <nixpkgs> { overlays = [ overlay1 overlay2 ]; }.

NOTE: DO NOT USE THIS in nixpkgs. Further overlays can be added by calling the pkgs.extend or pkgs.appendOverlays, although it is often preferable to avoid these functions, because they recompute the Nixpkgs fixpoint, which is somewhat expensive to do.

Install overlays via configuration lookup

The list of overlays is determined as follows.

  1. First, if an overlays argument to the Nixpkgs function itself is given, then that is used and no path lookup will be performed.

  2. Otherwise, if the Nix path entry <nixpkgs-overlays> exists, we look for overlays at that path, as described below.

    See the section on NIX_PATH in the Nix manual for more details on how to set a value for <nixpkgs-overlays>.

  3. If one of ~/.config/nixpkgs/overlays.nix and ~/.config/nixpkgs/overlays/ exists, then we look for overlays at that path, as described below. It is an error if both exist.

If we are looking for overlays at a path, then there are two cases:

  • If the path is a file, then the file is imported as a Nix expression and used as the list of overlays.

  • If the path is a directory, then we take the content of the directory, order it lexicographically, and attempt to interpret each as an overlay by:

    • Importing the file, if it is a .nix file.

    • Importing a top-level default.nix file, if it is a directory.

Because overlays that are set in NixOS configuration do not affect non-NixOS operations such as nix-env, the overlays.nix option provides a convenient way to use the same overlays for a NixOS system configuration and user configuration: the same file can be used as overlays.nix and imported as the value of nixpkgs.overlays.

Defining overlays

Overlays are Nix functions which accept two arguments, conventionally called either final and prev in newer code or self and super in older code, and return a set of packages. For example, the following is a valid overlay.

final: prev:

{
  boost = prev.boost.override { python = final.python3; };
  rr = prev.callPackage ./pkgs/rr { stdenv = final.stdenv_32bit; };
}

The first argument (final, self) corresponds to the final package set. You should use this set for the dependencies of all packages specified in your overlay. For example, all the dependencies of rr in the example above come from final, as well as the overridden dependencies used in the boost override.

The second argument (prev, super) corresponds to the result of the evaluation of the previous stages of Nixpkgs. It does not contain any of the packages added by the current overlay, nor any of the following overlays. This set should be used either to refer to packages you wish to override, or to access functions defined in Nixpkgs. For example, the original recipe of boost in the above example, comes from prev, as well as the callPackage function.

The value returned by this function should be a set similar to pkgs/top-level/all-packages.nix, containing overridden and/or new packages.

Overlays are similar to other methods for customizing Nixpkgs, in particular the packageOverrides attribute described in the section called “Modify packages via packageOverrides. Indeed, packageOverrides acts as an overlay with only the prev argument. It is therefore appropriate for basic use, but overlays are more powerful and easier to distribute.

Using overlays to configure alternatives

Certain software packages have different implementations of the same interface. Other distributions have functionality to switch between these. For example, Debian provides DebianAlternatives. Nixpkgs has what we call alternatives, which are configured through overlays.

BLAS/LAPACK

In Nixpkgs, we have multiple implementations of the BLAS/LAPACK numerical linear algebra interfaces. They are:

  • OpenBLAS

    The Nixpkgs attribute is openblas for ILP64 (integer width = 64 bits) and openblasCompat for LP64 (integer width = 32 bits). openblasCompat is the default.

  • LAPACK reference (also provides BLAS and CBLAS)

    The Nixpkgs attribute is lapack-reference.

  • Intel MKL (only works on the x86_64 architecture, unfree)

    The Nixpkgs attribute is mkl.

  • BLIS

    BLIS, available through the attribute blis, is a framework for linear algebra kernels. In addition, it implements the BLAS interface.

  • AMD BLIS/LIBFLAME (optimized for modern AMD x86_64 CPUs)

    The AMD fork of the BLIS library, with attribute amd-blis, extends BLIS with optimizations for modern AMD CPUs. The changes are usually submitted to the upstream BLIS project after some time. However, AMD BLIS typically provides some performance improvements on AMD Zen CPUs. The complementary AMD LIBFLAME library, with attribute amd-libflame, provides a LAPACK implementation.

Introduced in PR #83888, we are able to override the blas and lapack packages to use different implementations, through the blasProvider and lapackProvider argument. This can be used to select a different provider. BLAS providers will have symlinks in $out/lib/libblas.so.3 and $out/lib/libcblas.so.3 to their respective BLAS libraries. Likewise, LAPACK providers will have symlinks in $out/lib/liblapack.so.3 and $out/lib/liblapacke.so.3 to their respective LAPACK libraries. For example, Intel MKL is both a BLAS and LAPACK provider. An overlay can be created to use Intel MKL that looks like:

final: prev:

{
  blas = prev.blas.override { blasProvider = final.mkl; };

  lapack = prev.lapack.override { lapackProvider = final.mkl; };
}

This overlay uses Intel’s MKL library for both BLAS and LAPACK interfaces. Note that the same can be accomplished at runtime using LD_LIBRARY_PATH of libblas.so.3 and liblapack.so.3. For instance:

$ LD_LIBRARY_PATH=$(nix-build -A mkl)/lib${LD_LIBRARY_PATH:+:}$LD_LIBRARY_PATH nix-shell -p octave --run octave

Intel MKL requires an openmp implementation when running with multiple processors. By default, mkl will use Intel’s iomp implementation if no other is specified, but this is a runtime-only dependency and binary compatible with the LLVM implementation. To use that one instead, Intel recommends users set it with LD_PRELOAD. Note that mkl is only available on x86_64-linux and x86_64-darwin. Moreover, Hydra is not building and distributing pre-compiled binaries using it.

To override blas and lapack with its reference implementations (i.e. for development purposes), one can use the following overlay:

final: prev:

{
  blas = prev.blas.override { blasProvider = final.lapack-reference; };

  lapack = prev.lapack.override { lapackProvider = final.lapack-reference; };
}

For BLAS/LAPACK switching to work correctly, all packages must depend on blas or lapack. This ensures that only one BLAS/LAPACK library is used at one time. There are two versions of BLAS/LAPACK currently in the wild, LP64 (integer size = 32 bits) and ILP64 (integer size = 64 bits). The attributes blas and lapack are LP64 by default. Their ILP64 version are provided through the attributes blas-ilp64 and lapack-ilp64. Some software needs special flags or patches to work with ILP64. You can check if ILP64 is used in Nixpkgs with blas.isILP64 and lapack.isILP64. Some software does NOT work with ILP64, and derivations need to specify an assertion to prevent this. You can prevent ILP64 from being used with the following:

{
  stdenv,
  blas,
  lapack,
  ...
}:

assert (!blas.isILP64) && (!lapack.isILP64);

stdenv.mkDerivation {
  # ...
}

Switching the MPI implementation

All programs that are built with MPI support use the generic attribute mpi as an input. At the moment Nixpkgs natively provides the following MPI implementations:

  • Open MPI (default), attribute name openmpi

  • MPICH, attribute name mpich

  • MVAPICH, attribute name mvapich

To provide MPI enabled applications that use MPICH, instead of the default Open MPI, use the following overlay:

final: prev:

{
  mpi = final.mpich;
}

Overriding

Sometimes one wants to override parts of nixpkgs, e.g. derivation attributes, the results of derivations.

These functions are used to make changes to packages, returning only single packages. Overlays, on the other hand, can be used to combine the overridden packages across the entire package set of Nixpkgs.

<pkg>.override

The function override is usually available for all the derivations in the nixpkgs expression (pkgs).

It is used to override the arguments passed to a function.

Example usages:

pkgs.foo.override {
  arg1 = val1;
  arg2 = val2; # ...
}

It’s also possible to access the previous arguments.

pkgs.foo.override (previous: {
  arg1 = previous.arg1; # ...
})
import pkgs.path {
  overlays = [ (self: super: { foo = super.foo.override { barSupport = true; }; }) ];
}
{
  mypkg = pkgs.callPackage ./mypkg.nix {
    mydep = pkgs.mydep.override {
      # ...
    };
  };
}

In the first example, pkgs.foo is the result of a function call with some default arguments, usually a derivation. Using pkgs.foo.override will call the same function with the given new arguments.

Many packages, like the foo example above, provide package options with default values in their arguments, to facilitate overriding. Because it’s not usually feasible to test that packages build with all combinations of options, you might find that a package doesn’t build if you override options to non-default values.

Package maintainers are not expected to fix arbitrary combinations of options. If you find that something doesn’t work, please submit a fix, ideally with a regression test. If you want to ensure that things keep working, consider becoming a maintainer for the package.

<pkg>.overrideAttrs

The function overrideAttrs allows overriding the attribute set passed to a stdenv.mkDerivation call, producing a new derivation based on the original one. This function is available on all derivations produced by the stdenv.mkDerivation function, which is most packages in the Nixpkgs expression pkgs.

Example usages:

{
  helloBar = pkgs.hello.overrideAttrs (
    finalAttrs: previousAttrs: { pname = previousAttrs.pname + "-bar"; }
  );
}

In the above example, “-bar” is appended to the pname attribute, while all other attributes will be retained from the original hello package.

The argument previousAttrs is conventionally used to refer to the attr set originally passed to stdenv.mkDerivation.

The argument finalAttrs refers to the final attributes passed to mkDerivation, plus the finalPackage attribute which is equal to the result of mkDerivation or subsequent overrideAttrs calls.

If only a one-argument function is written, the argument has the meaning of previousAttrs.

Function arguments can be omitted entirely if there is no need to access previousAttrs or finalAttrs.

{ helloWithDebug = pkgs.hello.overrideAttrs { separateDebugInfo = true; }; }

In the above example, the separateDebugInfo attribute is overridden to be true, thus building debug info for helloWithDebug.

Note

Note that separateDebugInfo is processed only by the stdenv.mkDerivation function, not the generated, raw Nix derivation. Thus, using overrideDerivation will not work in this case, as it overrides only the attributes of the final derivation. It is for this reason that overrideAttrs should be preferred in (almost) all cases to overrideDerivation, i.e. to allow using stdenv.mkDerivation to process input arguments, as well as the fact that it is easier to use (you can use the same attribute names you see in your Nix code, instead of the ones generated (e.g. buildInputs vs nativeBuildInputs), and it involves less typing).

<pkg>.overrideDerivation

Warning

You should prefer overrideAttrs in almost all cases, see its documentation for the reasons why. overrideDerivation is not deprecated and will continue to work, but is less nice to use and does not have as many abilities as overrideAttrs.

Warning

Do not use this function in Nixpkgs as it evaluates a derivation before modifying it, which breaks package abstraction. In addition, this evaluation-per-function application incurs a performance penalty, which can become a problem if many overrides are used. It is only intended for ad-hoc customisation, such as in ~/.config/nixpkgs/config.nix.

The function overrideDerivation creates a new derivation based on an existing one by overriding the original’s attributes with the attribute set produced by the specified function. This function is available on all derivations defined using the makeOverridable function. Most standard derivation-producing functions, such as stdenv.mkDerivation, are defined using this function, which means most packages in the Nixpkgs expression, pkgs, have this function.

Example usage:

{
  mySed = pkgs.gnused.overrideDerivation (oldAttrs: {
    name = "sed-4.2.2-pre";
    src = fetchurl {
      url = "ftp://alpha.gnu.org/gnu/sed/sed-4.2.2-pre.tar.bz2";
      hash = "sha256-MxBJRcM2rYzQYwJ5XKxhXTQByvSg5jZc5cSHEZoB2IY=";
    };
    patches = [ ];
  });
}

In the above example, the name, src, and patches of the derivation will be overridden, while all other attributes will be retained from the original derivation.

The argument oldAttrs is used to refer to the attribute set of the original derivation.

Note

A package’s attributes are evaluated before being modified by the overrideDerivation function. For example, the name attribute reference in url = "mirror://gnu/hello/${name}.tar.gz"; is filled-in before the overrideDerivation function modifies the attribute set. This means that overriding the name attribute, in this example, will not change the value of the url attribute. Instead, we need to override both the name and url attributes.

lib.makeOverridable

The function lib.makeOverridable is used to make the result of a function easily customizable. This utility only makes sense for functions that accept an argument set and return an attribute set.

Example usage:

{
  f =
    { a, b }:
    {
      result = a + b;
    };
  c = lib.makeOverridable f {
    a = 1;
    b = 2;
  };
}

The variable c is the value of the f function applied with some default arguments. Hence the value of c.result is 3, in this example.

The variable c however also has some additional functions, like c.override which can be used to override the default arguments. In this example the value of (c.override { a = 4; }).result is 6.

Nixpkgs lib

Functions reference

The Nixpkgs repository has several utility functions to manipulate Nix expressions.

Nixpkgs Library Functions

Nixpkgs provides a standard library at pkgs.lib, or through import <nixpkgs/lib>.

lib.asserts: assertion functions

lib.asserts.assertMsg

Throw if pred is false, else return pred. Intended to be used to augment asserts with helpful error messages.

Inputs
pred

Predicate that needs to succeed, otherwise msg is thrown

msg

Message to throw in case pred fails

Type
assertMsg :: Bool -> String -> Bool
Examples
Example 1. lib.asserts.assertMsg usage example
assertMsg false "nope"
stderr> error: nope
assert assertMsg ("foo" == "bar") "foo is not bar, silly"; ""
stderr> error: foo is not bar, silly

Located at lib/asserts.nix:50 in <nixpkgs>.

lib.asserts.assertOneOf

Specialized assertMsg for checking if val is one of the elements of the list xs. Useful for checking enums.

Inputs
name

The name of the variable the user entered val into, for inclusion in the error message

val

The value of what the user provided, to be compared against the values in xs

xs

The list of valid values

Type
assertOneOf :: String -> ComparableVal -> [ComparableVal] -> Bool
Examples
Example 2. lib.asserts.assertOneOf usage example
let sslLibrary = "libressl";
in assertOneOf "sslLibrary" sslLibrary [ "openssl" "bearssl" ]
stderr> error: sslLibrary must be one of [
stderr>   "openssl"
stderr>   "bearssl"
stderr> ], but is: "libressl"

Located at lib/asserts.nix:91 in <nixpkgs>.

lib.asserts.assertEachOneOf

Specialized assertMsg for checking if every one of vals is one of the elements of the list xs. Useful for checking lists of supported attributes.

Inputs
name

The name of the variable the user entered val into, for inclusion in the error message

vals

The list of values of what the user provided, to be compared against the values in xs

xs

The list of valid values

Type
assertEachOneOf :: String -> [ComparableVal] -> [ComparableVal] -> Bool
Examples
Example 3. lib.asserts.assertEachOneOf usage example
let sslLibraries = [ "libressl" "bearssl" ];
in assertEachOneOf "sslLibraries" sslLibraries [ "openssl" "bearssl" ]
stderr> error: each element in sslLibraries must be one of [
stderr>   "openssl"
stderr>   "bearssl"
stderr> ], but is: [
stderr>   "libressl"
stderr>   "bearssl"
stderr> ]

Located at lib/asserts.nix:139 in <nixpkgs>.

lib.asserts.checkAssertWarn

Wrap a value with logic that throws an error when assertions fail and emits any warnings.

Inputs
assertions

A list of assertions. If any of their assertion attrs is false, their message attrs will be emitted in a throw.

warnings

A list of strings to emit as warnings. This function does no filtering on this list.

val

A value to return, wrapped in warn, if a throw is not necessary.

Type
checkAssertWarn :: [{ assertion :: Bool; message :: String; }] -> [String] -> a -> a
Examples
Example 4. lib.asserts.checkAssertWarn usage example
checkAssertWarn
  [ { assertion = false; message = "Will fail"; } ]
  [ ]
  null
stderr>        error:
stderr>        Failed assertions:
stderr>        - Will fail

checkAssertWarn
  [ { assertion = true; message = "Will not fail"; } ]
  [ "Will warn" ]
  null
stderr> evaluation warning: Will warn
null

Located at lib/asserts.nix:192 in <nixpkgs>.

lib.attrsets: attribute set functions

Operations on attribute sets.

lib.attrsets.attrByPath

Returns an attribute from nested attribute sets.

Nix has an attribute selection operator . which is sufficient for such queries, as long as the number of attributes is static. For example:

(x.a.b or 6) == attrByPath ["a" "b"] 6 x
# and
(x.${f p}."example.com" or 6) == attrByPath [ (f p) "example.com" ] 6 x
Inputs
attrPath

A list of strings representing the attribute path to return from set

default

Default value if attrPath does not resolve to an existing value

set

The nested attribute set to select values from

Type
attrByPath :: [String] -> Any -> AttrSet -> Any
Examples
Example 5. lib.attrsets.attrByPath usage example
x = { a = { b = 3; }; }
# ["a" "b"] is equivalent to x.a.b
# 6 is a default value to return if the path does not exist in attrset
attrByPath ["a" "b"] 6 x
=> 3
attrByPath ["z" "z"] 6 x
=> 6

Located at lib/attrsets.nix:88 in <nixpkgs>.

lib.attrsets.hasAttrByPath

Returns if an attribute from nested attribute set exists.

Nix has a has attribute operator ?, which is sufficient for such queries, as long as the number of attributes is static. For example:

(x?a.b) == hasAttrByPath ["a" "b"] x
# and
(x?${f p}."example.com") == hasAttrByPath [ (f p) "example.com" ] x

Laws:

  1. hasAttrByPath [] x == true
    
Inputs
attrPath

A list of strings representing the attribute path to check from set

set

The nested attribute set to check

Type
hasAttrByPath :: [String] -> AttrSet -> Bool
Examples
Example 6. lib.attrsets.hasAttrByPath usage example
x = { a = { b = 3; }; }
hasAttrByPath ["a" "b"] x
=> true
hasAttrByPath ["z" "z"] x
=> false
hasAttrByPath [] (throw "no need")
=> true

Located at lib/attrsets.nix:156 in <nixpkgs>.

lib.attrsets.longestValidPathPrefix

Returns the longest prefix of an attribute path that refers to an existing attribute in a nesting of attribute sets.

Can be used after mapAttrsRecursiveCond to apply a condition, although this will evaluate the predicate function on sibling attributes as well.

Note that the empty attribute path is valid for all values, so this function only throws an exception if any of its inputs does.

Laws:

  1. attrsets.longestValidPathPrefix [] x == []
    
  2. hasAttrByPath (attrsets.longestValidPathPrefix p x) x == true
    
Inputs
attrPath

A list of strings representing the longest possible path that may be returned.

v

The nested attribute set to check.

Type
longestValidPathPrefix :: [String] -> AttrSet -> [String]
Examples
Example 7. lib.attrsets.longestValidPathPrefix usage example
x = { a = { b = 3; }; }
attrsets.longestValidPathPrefix ["a" "b" "c"] x
=> ["a" "b"]
attrsets.longestValidPathPrefix ["a"] x
=> ["a"]
attrsets.longestValidPathPrefix ["z" "z"] x
=> []
attrsets.longestValidPathPrefix ["z" "z"] (throw "no need")
=> []

Located at lib/attrsets.nix:225 in <nixpkgs>.

lib.attrsets.setAttrByPath

Create a new attribute set with value set at the nested attribute location specified in attrPath.

Inputs
attrPath

A list of strings representing the attribute path to set

value

The value to set at the location described by attrPath

Type
setAttrByPath :: [String] -> Any -> AttrSet
Examples
Example 8. lib.attrsets.setAttrByPath usage example
setAttrByPath ["a" "b"] 3
=> { a = { b = 3; }; }

Located at lib/attrsets.nix:285 in <nixpkgs>.

lib.attrsets.getAttrFromPath

Like attrByPath, but without a default value. If it doesn’t find the path it will throw an error.

Nix has an attribute selection operator which is sufficient for such queries, as long as the number of attributes is static. For example:

x.a.b == getAttrFromPath ["a" "b"] x
# and
x.${f p}."example.com" == getAttrFromPath [ (f p) "example.com" ] x
Inputs
attrPath

A list of strings representing the attribute path to get from set

set

The nested attribute set to find the value in.

Type
getAttrFromPath :: [String] -> AttrSet -> Any
Examples
Example 9. lib.attrsets.getAttrFromPath usage example
x = { a = { b = 3; }; }
getAttrFromPath ["a" "b"] x
=> 3
getAttrFromPath ["z" "z"] x
=> error: cannot find attribute `z.z'

Located at lib/attrsets.nix:335 in <nixpkgs>.

lib.attrsets.concatMapAttrs

Map each attribute in the given set and merge them into a new attribute set.

Inputs
f

1. Function argument

v

2. Function argument

Type
concatMapAttrs :: (String -> Any -> AttrSet) -> AttrSet -> AttrSet
Examples
Example 10. lib.attrsets.concatMapAttrs usage example
concatMapAttrs
  (name: value: {
    ${name} = value;
    ${name + value} = value;
  })
  { x = "a"; y = "b"; }
=> { x = "a"; xa = "a"; y = "b"; yb = "b"; }

Located at lib/attrsets.nix:374 in <nixpkgs>.

lib.attrsets.updateManyAttrsByPath

Update or set specific paths of an attribute set.

Takes a list of updates to apply and an attribute set to apply them to, and returns the attribute set with the updates applied. Updates are represented as { path = ...; update = ...; } values, where path is a list of strings representing the attribute path that should be updated, and update is a function that takes the old value at that attribute path as an argument and returns the new value it should be.

Properties:

  • Updates to deeper attribute paths are applied before updates to more shallow attribute paths

  • Multiple updates to the same attribute path are applied in the order they appear in the update list

  • If any but the last path element leads into a value that is not an attribute set, an error is thrown

  • If there is an update for an attribute path that doesn’t exist, accessing the argument in the update function causes an error, but intermediate attribute sets are implicitly created as needed

Type
updateManyAttrsByPath :: [{ path :: [String]; update :: (Any -> Any); }] -> AttrSet -> AttrSet
Examples
Example 11. lib.attrsets.updateManyAttrsByPath usage example
updateManyAttrsByPath [
  {
    path = [ "a" "b" ];
    update = old: { d = old.c; };
  }
  {
    path = [ "a" "b" "c" ];
    update = old: old + 1;
  }
  {
    path = [ "x" "y" ];
    update = old: "xy";
  }
] { a.b.c = 0; }
=> { a = { b = { d = 1; }; }; x = { y = "xy"; }; }

Located at lib/attrsets.nix:436 in <nixpkgs>.

lib.attrsets.attrVals

Returns the specified attributes from a set.

Inputs
nameList

The list of attributes to fetch from set. Each attribute name must exist on the attribute set

set

The set to get attribute values from

Type
attrVals :: [String] -> { [String] :: a } -> [a]
Examples
Example 12. lib.attrsets.attrVals usage example
attrVals ["a" "b" "c"] as
=> [as.a as.b as.c]

Located at lib/attrsets.nix:535 in <nixpkgs>.

lib.attrsets.attrValues

Returns the values of all attributes in the given set, sorted by attribute name.

Type
attrValues :: { [String] :: a } -> [a]
Examples
Example 13. lib.attrsets.attrValues usage example
attrValues {c = 3; a = 1; b = 2;}
=> [1 2 3]

Located at lib/attrsets.nix:558 in <nixpkgs>.

lib.attrsets.getAttrs

Given a set of attribute names, return the set of the corresponding attributes from the given set.

Inputs
names

A list of attribute names to get out of set

set

The set to get the named attributes from

Type
getAttrs :: [String] -> { [String] :: a } -> { [String] :: a }
Examples
Example 14. lib.attrsets.getAttrs usage example
getAttrs [ "a" "b" ] { a = 1; b = 2; c = 3; }
=> { a = 1; b = 2; }

Located at lib/attrsets.nix:591 in <nixpkgs>.

lib.attrsets.catAttrs

Collect each attribute named attr from a list of attribute sets. Sets that don’t contain the named attribute are ignored.

Inputs
attr

The attribute name to get out of the sets.

list

The list of attribute sets to go through

Type
catAttrs :: String -> [{ [String] :: a }] -> [a]
Examples
Example 15. lib.attrsets.catAttrs usage example
catAttrs "a" [{a = 1;} {b = 0;} {a = 2;}]
=> [1 2]

Located at lib/attrsets.nix:624 in <nixpkgs>.

lib.attrsets.filterAttrs

Filter an attribute set by removing all attributes for which the given predicate return false.

Inputs
pred

Predicate taking an attribute name and an attribute value, which returns true to include the attribute, or false to exclude the attribute.

If possible, decide on name first and on value only if necessary. This avoids evaluating the value if the name is already enough, making it possible, potentially, to have the argument reference the return value. (Depending on context, that could still be considered a self reference by users; a common pattern in Nix.)

filterAttrs is occasionally the cause of infinite recursion in configuration systems that allow self-references. To support the widest range of user-provided logic, perform the filterAttrs call as late as possible. Typically that’s right before using it in a derivation, as opposed to an implicit conversion whose result is accessible to the user’s expressions.

set

The attribute set to filter

Type
filterAttrs :: (String -> a -> Bool) -> { [String] :: a } -> { [String] :: a }
Examples
Example 16. lib.attrsets.filterAttrs usage example
filterAttrs (n: v: n == "foo") { foo = 1; bar = 2; }
=> { foo = 1; }

Located at lib/attrsets.nix:667 in <nixpkgs>.

lib.attrsets.filterAttrsRecursive

Filter an attribute set recursively by removing all attributes for which the given predicate return false.

Inputs
pred

Predicate taking an attribute name and an attribute value, which returns true to include the attribute, or false to exclude the attribute.

set

The attribute set to filter

Type
filterAttrsRecursive :: (String -> Any -> Bool) -> AttrSet -> AttrSet
Examples
Example 17. lib.attrsets.filterAttrsRecursive usage example
filterAttrsRecursive (n: v: v != null) { foo = { bar = null; }; }
=> { foo = {}; }

Located at lib/attrsets.nix:700 in <nixpkgs>.

lib.attrsets.foldlAttrs

Like lib.lists.foldl' but for attribute sets. Iterates over every name-value pair in the given attribute set. The result of the callback function is often called acc for accumulator. It is passed between callbacks from left to right and the final acc is the return value of foldlAttrs.

Note

There is a completely different function lib.foldAttrs which has nothing to do with this function, despite the similar name.

Inputs
f

1. Function argument

init

2. Function argument

set

3. Function argument

Type
foldlAttrs :: ( a -> String -> b -> a ) -> a -> { [String] :: b } -> a
Examples
Example 18. lib.attrsets.foldlAttrs usage example
foldlAttrs
  (acc: name: value: {
    sum = acc.sum + value;
    names = acc.names ++ [name];
  })
  { sum = 0; names = []; }
  {
    foo = 1;
    bar = 10;
  }
->
  {
    sum = 11;
    names = ["bar" "foo"];
  }

foldlAttrs
  (throw "function not needed")
  123
  {};
->
  123

foldlAttrs
  (acc: _: _: acc)
  3
  { z = throw "value not needed"; a = throw "value not needed"; };
->
  3

The accumulator doesn't have to be an attrset.
It can be as simple as a number or string.

foldlAttrs
  (acc: _: v: acc * 10 + v)
  1
  { z = 1; a = 2; };
->
  121

Located at lib/attrsets.nix:795 in <nixpkgs>.

lib.attrsets.foldAttrs

Apply fold functions to values grouped by key.

Inputs
op

A function, given a value and a collector combines the two.

nul

The starting value.

list_of_attrs

A list of attribute sets to fold together by key.

Type
foldAttrs :: (a -> b -> b) -> b -> [{ [String] :: a }] -> { [String] :: b }
Examples
Example 19. lib.attrsets.foldAttrs usage example
foldAttrs (item: acc: [item] ++ acc) [] [{ a = 2; } { a = 3; }]
=> { a = [ 2 3 ]; }

Located at lib/attrsets.nix:833 in <nixpkgs>.

lib.attrsets.collect

Recursively collect sets that verify a given predicate named pred from the set attrs. The recursion is stopped when the predicate is verified.

Inputs
pred

Given an attribute’s value, determine if recursion should stop.

attrs

The attribute set to recursively collect.

Type
collect :: (AttrSet -> Bool) -> AttrSet -> [Any]
Examples
Example 20. lib.attrsets.collect usage example
collect isList { a = { b = ["b"]; }; c = [1]; }
=> [["b"] [1]]

collect (x: x ? outPath)
   { a = { outPath = "a/"; }; b = { outPath = "b/"; }; }
=> [{ outPath = "a/"; } { outPath = "b/"; }]

Located at lib/attrsets.nix:875 in <nixpkgs>.

lib.attrsets.cartesianProduct

Return the cartesian product of attribute set value combinations.

Inputs
attrsOfLists

Attribute set with attributes that are lists of values

Type
cartesianProduct :: { [String] :: [a] } -> [{ [String] :: a }]
Examples
Example 21. lib.attrsets.cartesianProduct usage example
cartesianProduct { a = [ 1 2 ]; b = [ 10 20 ]; }
=> [
     { a = 1; b = 10; }
     { a = 1; b = 20; }
     { a = 2; b = 10; }
     { a = 2; b = 20; }
   ]

Located at lib/attrsets.nix:915 in <nixpkgs>.

lib.attrsets.mapCartesianProduct

Return the result of function f applied to the cartesian product of attribute set value combinations. Equivalent to using cartesianProduct followed by map.

Inputs
f

A function, given an attribute set, it returns a new value.

attrsOfLists

Attribute set with attributes that are lists of values

Type
mapCartesianProduct :: ({ [String] :: a } -> b) -> { [String] :: a } -> [b]
Examples
Example 22. lib.attrsets.mapCartesianProduct usage example
mapCartesianProduct ({a, b}: "${a}-${b}") { a = [ "1" "2" ]; b = [ "3" "4" ]; }
=> [ "1-3" "1-4" "2-3" "2-4" ]

Located at lib/attrsets.nix:955 in <nixpkgs>.

lib.attrsets.nameValuePair

Utility function that creates a {name, value} pair as expected by builtins.listToAttrs.

Inputs
name

Attribute name

value

Attribute value

Type
nameValuePair :: String -> a -> { name :: String; value :: a; }
Examples
Example 23. lib.attrsets.nameValuePair usage example
nameValuePair "some" 6
=> { name = "some"; value = 6; }

Located at lib/attrsets.nix:987 in <nixpkgs>.

lib.attrsets.mapAttrs

Apply a function to each element in an attribute set, creating a new attribute set.

Inputs
f

A function that takes an attribute name and its value, and returns the new value for the attribute.

attrset

The attribute set to iterate through.

Type
mapAttrs :: (String -> a -> b) -> { [String] :: a } -> { [String] :: b }
Examples
Example 24. lib.attrsets.mapAttrs usage example
mapAttrs (name: value: name + "-" + value)
   { x = "foo"; y = "bar"; }
=> { x = "x-foo"; y = "y-bar"; }

Located at lib/attrsets.nix:1020 in <nixpkgs>.

lib.attrsets.mapAttrs'

Like mapAttrs, but allows the name of each attribute to be changed in addition to the value. The applied function should return both the new name and value as a nameValuePair.

Inputs
f

A function, given an attribute’s name and value, returns a new nameValuePair.

set

Attribute set to map over.

Type
mapAttrs' :: (String -> a -> { name :: String; value :: b; }) -> { [String] :: a } -> { [String] :: b }
Examples
Example 25. lib.attrsets.mapAttrs' usage example
mapAttrs' (name: value: nameValuePair ("foo_" + name) ("bar-" + value))
   { x = "a"; y = "b"; }
=> { foo_x = "bar-a"; foo_y = "bar-b"; }

Located at lib/attrsets.nix:1055 in <nixpkgs>.

lib.attrsets.mapAttrsToList

Call a function for each attribute in the given set and return the result in a list.

Inputs
f

A function, given an attribute’s name and value, returns a new value.

attrs

Attribute set to map over.

Type
mapAttrsToList :: (String -> a -> b) -> { [String] :: a } -> [b]
Examples
Example 26. lib.attrsets.mapAttrsToList usage example
mapAttrsToList (name: value: name + value)
   { x = "a"; y = "b"; }
=> [ "xa" "yb" ]

Located at lib/attrsets.nix:1089 in <nixpkgs>.

lib.attrsets.attrsToList

Deconstruct an attrset to a list of name-value pairs as expected by builtins.listToAttrs. Each element of the resulting list is an attribute set with these attributes:

  • name (string): The name of the attribute

  • value (any): The value of the attribute

The following is always true:

builtins.listToAttrs (attrsToList attrs) == attrs

Warning

The opposite is not always true. In general expect that

attrsToList (builtins.listToAttrs list) != list

This is because the listToAttrs removes duplicate names and doesn’t preserve the order of the list.

Inputs
set

The attribute set to deconstruct.

Type
attrsToList :: { [String] :: a } -> [{ name :: String; value :: a; }]
Examples
Example 27. lib.attrsets.attrsToList usage example
attrsToList { foo = 1; bar = "asdf"; }
=> [ { name = "bar"; value = "asdf"; } { name = "foo"; value = 1; } ]

Located at lib/attrsets.nix:1134 in <nixpkgs>.

lib.attrsets.mapAttrsRecursive

Like mapAttrs, except that it recursively applies itself to the leaf attributes of a potentially-nested attribute set: the second argument of the function will never be an attrset. Also, the first argument of the mapping function is a list of the attribute names that form the path to the leaf attribute.

For a function that gives you control over what counts as a leaf, see mapAttrsRecursiveCond.

Example 28. Map over leaf attributes
mapAttrsRecursive (path: value: concatStringsSep "-" (path ++ [value]))
  { n = { a = "A"; m = { b = "B"; c = "C"; }; }; d = "D"; }

evaluates to

{ n = { a = "n-a-A"; m = { b = "n-m-b-B"; c = "n-m-c-C"; }; }; d = "d-D"; }

Type
mapAttrsRecursive :: ([String] -> a -> b) -> AttrSet -> AttrSet

Located at lib/attrsets.nix:1161 in <nixpkgs>.

lib.attrsets.mapAttrsRecursiveCond

Like mapAttrsRecursive, but it takes an additional predicate that tells it whether to recurse into an attribute set. If the predicate returns false, mapAttrsRecursiveCond does not recurse, but instead applies the mapping function. If the predicate returns true, it does recurse, and does not apply the mapping function.

Example 29. Map over an leaf attributes defined by a condition

Map derivations to their name attribute. Derivatons are identified as attribute sets that contain { type = "derivation"; }.

mapAttrsRecursiveCond
  (as: !(as ? "type" && as.type == "derivation"))
  (path: x: x.name)
  attrs

Type
mapAttrsRecursiveCond :: (AttrSet -> Bool) -> ([String] -> a -> b) -> AttrSet -> AttrSet

Located at lib/attrsets.nix:1186 in <nixpkgs>.

lib.attrsets.mapAttrsToListRecursive

Apply a function to each leaf (non‐attribute‐set attribute) of a tree of nested attribute sets, returning the results of the function as a list, ordered lexicographically by their attribute paths.

Like mapAttrsRecursive, but concatenates the mapping function results into a list.

Inputs
f

Mapping function which, given an attribute’s path and value, returns a new value.

This value will be an element of the list returned by mapAttrsToListRecursive.

The first argument to the mapping function is a list of attribute names forming the path to the leaf attribute. The second argument is the leaf attribute value, which will never be an attribute set.

set

Attribute set to map over.

Type
mapAttrsToListRecursive :: ([String] -> a -> b) -> AttrSet -> [b]
Examples
Example 30. lib.attrsets.mapAttrsToListRecursive usage example
mapAttrsToListRecursive (path: value: "${concatStringsSep "." path}=${value}")
  { n = { a = "A"; m = { b = "B"; c = "C"; }; }; d = "D"; }
=> [ "n.a=A" "n.m.b=B" "n.m.c=C" "d=D" ]

Located at lib/attrsets.nix:1241 in <nixpkgs>.

lib.attrsets.mapAttrsToListRecursiveCond

Determine the nodes of a tree of nested attribute sets by applying a predicate, then apply a function to the leaves, returning the results as a list, ordered lexicographically by their attribute paths.

Like mapAttrsToListRecursive, but takes an additional predicate to decide whether to recurse into an attribute set.

Unlike mapAttrsRecursiveCond this predicate receives the attribute path as its first argument, in addition to the attribute set.

Inputs
pred

Predicate to decide whether to recurse into an attribute set.

If the predicate returns true, mapAttrsToListRecursiveCond recurses into the attribute set. If the predicate returns false, it does not recurse but instead applies the mapping function, treating the attribute set as a leaf.

The first argument to the predicate is a list of attribute names forming the path to the attribute set. The second argument is the attribute set.

f

Mapping function which, given an attribute’s path and value, returns a new value.

This value will be an element of the list returned by mapAttrsToListRecursiveCond.

The first argument to the mapping function is a list of attribute names forming the path to the leaf attribute. The second argument is the leaf attribute value, which may be an attribute set if the predicate returned false.

set

Attribute set to map over.

Type
mapAttrsToListRecursiveCond :: ([String] -> AttrSet -> Bool) -> ([String] -> a -> b) -> AttrSet -> [b]
Examples
Example 31. lib.attrsets.mapAttrsToListRecursiveCond usage example
mapAttrsToListRecursiveCond
  (path: as: !(lib.isDerivation as))
  (path: value: "--set=${lib.concatStringsSep "." path}=${toString value}")
  {
    rust.optimize = 2;
    target = {
      riscv64-unknown-linux-gnu.linker = pkgs.lld;
    };
  }
=> [ "--set=rust.optimize=2" "--set=target.riscv64-unknown-linux-gnu.linker=/nix/store/sjw4h1k…" ]

Located at lib/attrsets.nix:1308 in <nixpkgs>.

lib.attrsets.genAttrs

Generate an attribute set by mapping a function over a list of attribute names.

Inputs
names

Names of values in the resulting attribute set.

f

A function, given the name of the attribute, returns the attribute’s value.

Type
genAttrs :: [String] -> (String -> a) -> { [String] :: a }
Examples
Example 32. lib.attrsets.genAttrs usage example
genAttrs [ "foo" "bar" ] (name: "x_" + name)
=> { foo = "x_foo"; bar = "x_bar"; }

Located at lib/attrsets.nix:1348 in <nixpkgs>.

lib.attrsets.genAttrs'

Like genAttrs, but allows the name of each attribute to be specified in addition to the value. The applied function should return both the new name and value as a nameValuePair.

Warning

In case of attribute name collision the first entry determines the value, all subsequent conflicting entries for the same name are silently ignored.

Inputs
xs

A list of strings s used as generator.

f

A function, given a string s from the list xs, returns a new nameValuePair.

Type
genAttrs' :: [a] -> (a -> { name :: String; value :: b; }) -> { [String] :: b }
Examples
Example 33. lib.attrsets.genAttrs' usage example
genAttrs' [ "foo" "bar" ] (s: nameValuePair ("x_" + s) ("y_" + s))
=> { x_foo = "y_foo"; x_bar = "y_bar"; }

Located at lib/attrsets.nix:1385 in <nixpkgs>.

lib.attrsets.isDerivation

Check whether the argument is a derivation. Any set with { type = "derivation"; } counts as a derivation.

Inputs
value

Value to check.

Type
isDerivation :: Any -> Bool
Examples
Example 34. lib.attrsets.isDerivation usage example
nixpkgs = import <nixpkgs> {}
isDerivation nixpkgs.ruby
=> true
isDerivation "foobar"
=> false

Located at lib/attrsets.nix:1417 in <nixpkgs>.

lib.attrsets.toDerivation

Converts a store path to a fake derivation.

Inputs
path

A store path to convert to a derivation.

Type
toDerivation :: Path -> Derivation

Located at lib/attrsets.nix:1434 in <nixpkgs>.

lib.attrsets.optionalAttrs

If cond is true, return the attribute set as, otherwise an empty attribute set.

Inputs
cond

Condition under which the as attribute set is returned.

as

The attribute set to return if cond is true.

Type
optionalAttrs :: Bool -> AttrSet -> AttrSet
Examples
Example 35. lib.attrsets.optionalAttrs usage example
optionalAttrs (true) { my = "set"; }
=> { my = "set"; }
optionalAttrs (false) { my = "set"; }
=> { }

Located at lib/attrsets.nix:1482 in <nixpkgs>.

lib.attrsets.zipAttrsWithNames

Merge sets of attributes and use the function f to merge attributes values.

Inputs
names

List of attribute names to zip.

f

A function, accepts an attribute name, all the values, and returns a combined value.

sets

List of values from the list of attribute sets.

Type
zipAttrsWithNames :: [String] -> (String -> [a] -> b) -> [{ [String] :: a }] -> { [String] :: b }
Examples
Example 36. lib.attrsets.zipAttrsWithNames usage example
zipAttrsWithNames ["a"] (name: vs: vs) [{a = "x";} {a = "y"; b = "z";}]
=> { a = ["x" "y"]; }

Located at lib/attrsets.nix:1519 in <nixpkgs>.

lib.attrsets.zipAttrsWith

Merge sets of attributes and use the function f to merge attribute values. Like lib.attrsets.zipAttrsWithNames with all key names are passed for names.

Implementation note: Common names appear multiple times in the list of names, hopefully this does not affect the system because the maximal laziness avoid computing twice the same expression and listToAttrs does not care about duplicated attribute names.

Type
zipAttrsWith :: (String -> [a] -> b) -> [{ [String] :: a }] -> { [String] :: b }
Examples
Example 37. lib.attrsets.zipAttrsWith usage example
zipAttrsWith (name: values: values) [{a = "x";} {a = "y"; b = "z";}]
=> { a = ["x" "y"]; b = ["z"]; }

Located at lib/attrsets.nix:1554 in <nixpkgs>.

lib.attrsets.zipAttrs

Merge sets of attributes and combine each attribute value in to a list.

Like lib.attrsets.zipAttrsWith with (name: values: values) as the function.

Type
zipAttrs :: [{ [String] :: a }] -> { [String] :: [a] }
Examples
Example 38. lib.attrsets.zipAttrs usage example
zipAttrs [{a = "x";} {a = "y"; b = "z";}]
=> { a = ["x" "y"]; b = ["z"]; }

Located at lib/attrsets.nix:1579 in <nixpkgs>.

lib.attrsets.mergeAttrsList

Merge a list of attribute sets together using the // operator. In case of duplicate attributes, values from later list elements take precedence over earlier ones. The result is the same as foldl mergeAttrs { }, but the performance is better for large inputs. For n list elements, each with an attribute set containing m unique attributes, the complexity of this operation is O(nm log n).

Inputs
list

1. Function argument

Type
mergeAttrsList :: [AttrSet] -> AttrSet
Examples
Example 39. lib.attrsets.mergeAttrsList usage example
mergeAttrsList [ { a = 0; b = 1; } { c = 2; d = 3; } ]
=> { a = 0; b = 1; c = 2; d = 3; }
mergeAttrsList [ { a = 0; } { a = 1; } ]
=> { a = 1; }

Located at lib/attrsets.nix:1612 in <nixpkgs>.

lib.attrsets.recursiveUpdateUntil

Update lhs so that rhs wins for any given attribute path that occurs in both.

Unlike the // (update) operator, which operates on a single attribute set, This function views its operands lhs and rhs as a mapping from attribute paths to values.

The caller-provided function pred decides whether any given path is one of the following:

  • true: a value in the mapping

  • false: an attribute set whose purpose is to create the nesting structure.

Inputs
pred

Predicate function (of type List String -> Any -> Any -> Bool)

Inputs:

  • path : List String: the path to the current attribute as a list of strings for attribute names

  • lhsAtPath : Any: the value at that path in lhs; same as getAttrFromPath path lhs

  • rhsAtPath : Any: the value at that path in rhs; same as getAttrFromPath path rhs

Output:

  • true: path points to a value in the mapping, and rhsAtPath will appear in the return value of recursiveUpdateUntil

  • false: path is part of the nesting structure and will be an attrset in the return value of recursiveUpdateUntil

pred is only called for paths that extend prefixes for which pred returned false.

lhs

Left attribute set of the update.

rhs

Right attribute set of the update.

Type
recursiveUpdateUntil :: ([String] -> AttrSet -> AttrSet -> Bool) -> AttrSet -> AttrSet -> AttrSet
Examples
Example 40. lib.attrsets.recursiveUpdateUntil usage example
recursiveUpdateUntil (path: lhs: rhs: path == ["foo"]) {
  # left attribute set
  foo.bar = 1;
  foo.baz = 2;
  bar = 3;
} {
  # right attribute set
  foo.bar = 1;
  foo.quz = 2;
  baz = 4;
}

=> {
  foo.bar = 1; # 'foo.*' from the 'right' set
  foo.quz = 2; #
  bar = 3;     # 'bar' from the 'left' set
  baz = 4;     # 'baz' from the 'right' set
}

Located at lib/attrsets.nix:1706 in <nixpkgs>.

lib.attrsets.recursiveUpdate

A recursive variant of the update operator //. The recursion stops when one of the attribute values is not an attribute set, in which case the right hand side value takes precedence over the left hand side value.

Inputs
lhs

Left attribute set of the merge.

rhs

Right attribute set of the merge.

Type
recursiveUpdate :: AttrSet -> AttrSet -> AttrSet
Examples
Example 41. lib.attrsets.recursiveUpdate usage example
recursiveUpdate {
  boot.loader.grub.enable = true;
  boot.loader.grub.device = "/dev/hda";
} {
  boot.loader.grub.device = "";
}

returns: {
  boot.loader.grub.enable = true;
  boot.loader.grub.device = "";
}

Located at lib/attrsets.nix:1766 in <nixpkgs>.

lib.attrsets.matchAttrs

Recurse into every attribute set of the first argument and check that:

  • Each attribute path also exists in the second argument.

  • If the attribute’s value is not a nested attribute set, it must have the same value in the right argument.

Inputs
pattern

Attribute set structure to match

attrs

Attribute set to check

Type
matchAttrs :: AttrSet -> AttrSet -> Bool
Examples
Example 42. lib.attrsets.matchAttrs usage example
matchAttrs { cpu = {}; } { cpu = { bits = 64; }; }
=> true

Located at lib/attrsets.nix:1805 in <nixpkgs>.

lib.attrsets.overrideExisting

Override only the attributes that are already present in the old set useful for deep-overriding.

Inputs
old

Original attribute set

new

Attribute set with attributes to override in old.

Type
overrideExisting :: AttrSet -> AttrSet -> AttrSet
Examples
Example 43. lib.attrsets.overrideExisting usage example
overrideExisting {} { a = 1; }
=> {}
overrideExisting { b = 2; } { a = 1; }
=> { b = 2; }
overrideExisting { a = 3; b = 2; } { a = 1; }
=> { a = 1; b = 2; }

Located at lib/attrsets.nix:1858 in <nixpkgs>.

lib.attrsets.showAttrPath

Turns a list of strings into a human-readable description of those strings represented as an attribute path. The result of this function is not intended to be machine-readable. Create a new attribute set with value set at the nested attribute location specified in attrPath.

Inputs
path

Attribute path to render to a string

Type
showAttrPath :: [String] -> String
Examples
Example 44. lib.attrsets.showAttrPath usage example
showAttrPath [ "foo" "10" "bar" ]
=> "foo.\"10\".bar"
showAttrPath []
=> "<root attribute path>"

Located at lib/attrsets.nix:1891 in <nixpkgs>.

lib.attrsets.getOutput

Get a package output. If no output is found, fallback to .out and then to the default. The function is idempotent: getOutput "b" (getOutput "a" p) == getOutput "a" p.

Inputs
output

1. Function argument

pkg

2. Function argument

Type
getOutput :: String -> :: Derivation -> Derivation
Examples
Example 45. lib.attrsets.getOutput usage example
"${getOutput "dev" pkgs.openssl}"
=> "/nix/store/9rz8gxhzf8sw4kf2j2f1grr49w8zx5vj-openssl-1.0.1r-dev"

Located at lib/attrsets.nix:1927 in <nixpkgs>.

lib.attrsets.getFirstOutput

Get the first of the outputs provided by the package, or the default. This function is aligned with _overrideFirst() from the multiple-outputs.sh setup hook. Like getOutput, the function is idempotent.

Inputs
outputs

1. Function argument

pkg

2. Function argument

Type
getFirstOutput :: [String] -> Derivation -> Derivation
Examples
Example 46. lib.attrsets.getFirstOutput usage example
"${getFirstOutput [ "include" "dev" ] pkgs.openssl}"
=> "/nix/store/00000000000000000000000000000000-openssl-1.0.1r-dev"

Located at lib/attrsets.nix:1963 in <nixpkgs>.

lib.attrsets.getBin

Get a package’s bin output. If the output does not exist, fallback to .out and then to the default.

Inputs
pkg

The package whose bin output will be retrieved.

Type
getBin :: Derivation -> Derivation
Examples
Example 47. lib.attrsets.getBin usage example
"${getBin pkgs.openssl}"
=> "/nix/store/00000000000000000000000000000000-openssl-1.0.1r"

Located at lib/attrsets.nix:1998 in <nixpkgs>.

lib.attrsets.getLib

Get a package’s lib output. If the output does not exist, fallback to .out and then to the default.

Inputs
pkg

The package whose lib output will be retrieved.

Type
getLib :: Derivation -> Derivation
Examples
Example 48. lib.attrsets.getLib usage example
"${getLib pkgs.openssl}"
=> "/nix/store/9rz8gxhzf8sw4kf2j2f1grr49w8zx5vj-openssl-1.0.1r-lib"

Located at lib/attrsets.nix:2027 in <nixpkgs>.

lib.attrsets.getStatic

Get a package’s static output. If the output does not exist, fallback to .lib, then to .out, and then to the default.

Inputs
pkg

The package whose static output will be retrieved.

Type
getStatic :: Derivation -> Derivation
Examples
Example 49. lib.attrsets.getStatic usage example
"${lib.getStatic pkgs.glibc}"
=> "/nix/store/00000000000000000000000000000000-glibc-2.39-52-static"

Located at lib/attrsets.nix:2056 in <nixpkgs>.

lib.attrsets.getDev

Get a package’s dev output. If the output does not exist, fallback to .out and then to the default.

Inputs
pkg

The package whose dev output will be retrieved.

Type
getDev :: Derivation -> Derivation
Examples
Example 50. lib.attrsets.getDev usage example
"${getDev pkgs.openssl}"
=> "/nix/store/9rz8gxhzf8sw4kf2j2f1grr49w8zx5vj-openssl-1.0.1r-dev"

Located at lib/attrsets.nix:2089 in <nixpkgs>.

lib.attrsets.getInclude

Get a package’s include output. If the output does not exist, fallback to .dev, then to .out, and then to the default.

Inputs
pkg

The package whose include output will be retrieved.

Type
getInclude :: Derivation -> Derivation
Examples
Example 51. lib.attrsets.getInclude usage example
"${getInclude pkgs.openssl}"
=> "/nix/store/00000000000000000000000000000000-openssl-1.0.1r-dev"

Located at lib/attrsets.nix:2118 in <nixpkgs>.

lib.attrsets.getMan

Get a package’s man output. If the output does not exist, fallback to .out and then to the default.

Inputs
pkg

The package whose man output will be retrieved.

Type
getMan :: Derivation -> Derivation
Examples
Example 52. lib.attrsets.getMan usage example
"${getMan pkgs.openssl}"
=> "/nix/store/9rz8gxhzf8sw4kf2j2f1grr49w8zx5vj-openssl-1.0.1r-man"

Located at lib/attrsets.nix:2151 in <nixpkgs>.

lib.attrsets.chooseDevOutputs

Pick the outputs of packages to place in buildInputs

Inputs
pkgs

List of packages.

Type
chooseDevOutputs :: [Derivation] -> [Derivation]

Located at lib/attrsets.nix:2168 in <nixpkgs>.

lib.attrsets.recurseIntoAttrs

Make various Nix tools consider the contents of the resulting attribute set when looking for what to build, find, etc.

This function only affects a single attribute set; it does not apply itself recursively for nested attribute sets.

Inputs
attrs

An attribute set to scan for derivations.

Type
recurseIntoAttrs :: AttrSet -> AttrSet
Examples
Example 53. lib.attrsets.recurseIntoAttrs usage example
{ pkgs ? import <nixpkgs> {} }:
{
  myTools = pkgs.lib.recurseIntoAttrs {
    inherit (pkgs) hello figlet;
  };
}

Located at lib/attrsets.nix:2204 in <nixpkgs>.

lib.attrsets.dontRecurseIntoAttrs

Undo the effect of recurseIntoAttrs.

Inputs
attrs

An attribute set to not scan for derivations.

Type
dontRecurseIntoAttrs :: AttrSet -> AttrSet

Located at lib/attrsets.nix:2221 in <nixpkgs>.

lib.attrsets.unionOfDisjoint

unionOfDisjoint x y is equal to x // y, but accessing attributes present in both x and y will throw an error. This operator is commutative, unlike //.

Inputs
x

1. Function argument

y

2. Function argument

Type
unionOfDisjoint :: AttrSet -> AttrSet -> AttrSet

Located at lib/attrsets.nix:2243 in <nixpkgs>.

lib.strings: string manipulation functions

String manipulation functions.

lib.strings.join

Concatenates a list of strings with a separator between each element.

Inputs
sep

Separator to add between elements

list

List of strings that will be joined

Type
join :: String -> [String] -> String
Examples
Example 54. lib.strings.join usage example
join ", " ["foo" "bar"]
=> "foo, bar"

Located at lib/strings.nix:73 in <nixpkgs>.

lib.strings.concatStrings

Concatenate a list of strings.

Type
concatStrings :: [String] -> String
Examples
Example 55. lib.strings.concatStrings usage example
concatStrings ["foo" "bar"]
=> "foobar"

Located at lib/strings.nix:95 in <nixpkgs>.

lib.strings.concatMapStrings

Map a function over a list and concatenate the resulting strings.

Inputs
f

1. Function argument

list

2. Function argument

Type
concatMapStrings :: (a -> String) -> [a] -> String
Examples
Example 56. lib.strings.concatMapStrings usage example
concatMapStrings (x: "a" + x) ["foo" "bar"]
=> "afooabar"

Located at lib/strings.nix:125 in <nixpkgs>.

lib.strings.concatImapStrings

Like concatMapStrings except that the function f also gets the position as a parameter.

Inputs
f

1. Function argument

list

2. Function argument

Type
concatImapStrings :: (Int -> a -> String) -> [a] -> String
Examples
Example 57. lib.strings.concatImapStrings usage example
concatImapStrings (pos: x: "${toString pos}-${x}") ["foo" "bar"]
=> "1-foo2-bar"

Located at lib/strings.nix:156 in <nixpkgs>.

lib.strings.intersperse

Place an element between each element of a list

Inputs
separator

Separator to add between elements

list

Input list

Type
intersperse :: a -> [a] -> [a]
Examples
Example 58. lib.strings.intersperse usage example
intersperse "/" ["usr" "local" "bin"]
=> ["usr" "/" "local" "/" "bin"].

Located at lib/strings.nix:186 in <nixpkgs>.

lib.strings.concatStringsSep

Concatenate a list of strings with a separator between each element

Inputs
sep

Separator to add between elements

list

List of input strings

Type
concatStringsSep :: String -> [String] -> String
Examples
Example 59. lib.strings.concatStringsSep usage example
concatStringsSep "/" ["usr" "local" "bin"]
=> "usr/local/bin"

Located at lib/strings.nix:226 in <nixpkgs>.

lib.strings.concatMapStringsSep

Maps a function over a list of strings and then concatenates the result with the specified separator interspersed between elements.

Inputs
sep

Separator to add between elements

f

Function to map over the list

list

List of input strings

Type
concatMapStringsSep :: String -> (a -> String) -> [a] -> String
Examples
Example 60. lib.strings.concatMapStringsSep usage example
concatMapStringsSep "-" (x: toUpper x)  ["foo" "bar" "baz"]
=> "FOO-BAR-BAZ"

Located at lib/strings.nix:261 in <nixpkgs>.

lib.strings.concatImapStringsSep

Same as concatMapStringsSep, but the mapping function additionally receives the position of its argument.

Inputs
sep

Separator to add between elements

f

Function that receives elements and their positions

list

List of input strings

Type
concatIMapStringsSep :: String -> (Int -> a -> String) -> [a] -> String
Examples
Example 61. lib.strings.concatImapStringsSep usage example
concatImapStringsSep "-" (pos: x: toString (x / pos)) [ 6 6 6 ]
=> "6-3-2"

Located at lib/strings.nix:297 in <nixpkgs>.

lib.strings.concatMapAttrsStringSep

Like concatMapStringsSep but takes an attribute set instead of a list.

Inputs
sep

Separator to add between item strings

f

Function that takes each key and value and return a string

attrs

Attribute set to map from

Type
concatMapAttrsStringSep :: String -> (String -> a -> String) -> { [String] :: a } -> String
Examples
Example 62. lib.strings.concatMapAttrsStringSep usage example
concatMapAttrsStringSep "\n" (name: value: "${name}: foo-${value}") { a = "0.1.0"; b = "0.2.0"; }
=> "a: foo-0.1.0\nb: foo-0.2.0"

Located at lib/strings.nix:334 in <nixpkgs>.

lib.strings.concatLines

Concatenate a list of strings, adding a newline at the end of each one.

Inputs
list

List of strings. Any element that is not a string will be implicitly converted to a string.

Type
concatLines :: [String] -> String
Examples
Example 63. lib.strings.concatLines usage example
concatLines [ "foo" "bar" ]
=> "foo\nbar\n"

Located at lib/strings.nix:363 in <nixpkgs>.

lib.strings.replaceString

Given string s, replace every occurrence of the string from with the string to.

Inputs
from

The string to be replaced

to

The string to replace with

s

The original string where replacements will be made

Type
replaceString :: String -> String -> String -> String
Examples
Example 64. lib.strings.replaceString usage example
replaceString "world" "Nix" "Hello, world!"
=> "Hello, Nix!"
replaceString "." "_" "v1.2.3"
=> "v1_2_3"

Located at lib/strings.nix:398 in <nixpkgs>.

lib.strings.replicate

Repeat a string n times, and concatenate the parts into a new string.

Inputs
n

1. Function argument

s

2. Function argument

Type
replicate :: Int -> String -> String
Examples
Example 65. lib.strings.replicate usage example
replicate 3 "v"
=> "vvv"
replicate 5 "hello"
=> "hellohellohellohellohello"

Located at lib/strings.nix:431 in <nixpkgs>.

lib.strings.trim

Remove leading and trailing whitespace from a string s.

Whitespace is defined as any of the following characters: " ", “\t” “\r” “\n”

Inputs
s

The string to trim

Type
trim :: String -> String
Examples
Example 66. lib.strings.trim usage example
trim "   hello, world!   "
=> "hello, world!"

Located at lib/strings.nix:461 in <nixpkgs>.

lib.strings.trimWith

Remove leading and/or trailing whitespace from a string s.

To remove both leading and trailing whitespace, you can also use trim

Whitespace is defined as any of the following characters: " ", “\t” “\r” “\n”

Inputs
config (Attribute set)
start

Whether to trim leading whitespace (false by default)

end

Whether to trim trailing whitespace (false by default)

s

The string to trim

Type
trimWith :: { start :: Bool; end :: Bool; } -> String -> String
Examples
Example 67. lib.strings.trimWith usage example
trimWith { start = true; } "   hello, world!   "}
=> "hello, world!   "

trimWith { end = true; } "   hello, world!   "}
=> "   hello, world!"

Located at lib/strings.nix:505 in <nixpkgs>.

lib.strings.makeSearchPath

Construct a Unix-style, colon-separated search path consisting of the given subDir appended to each of the given paths.

Inputs
subDir

Directory name to append

paths

List of base paths

Type
makeSearchPath :: String -> [String] -> String
Examples
Example 68. lib.strings.makeSearchPath usage example
makeSearchPath "bin" ["/root" "/usr" "/usr/local"]
=> "/root/bin:/usr/bin:/usr/local/bin"
makeSearchPath "bin" [""]
=> "/bin"

Located at lib/strings.nix:566 in <nixpkgs>.

lib.strings.makeSearchPathOutput

Construct a Unix-style search path by appending the given subDir to the specified output of each of the packages.

If no output by the given name is found, fallback to .out and then to the default.

Inputs
output

Package output to use

subDir

Directory name to append

pkgs

List of packages

Type
makeSearchPathOutput :: String -> String -> [Derivation] -> String
Examples
Example 69. lib.strings.makeSearchPathOutput usage example
makeSearchPathOutput "dev" "bin" [ pkgs.openssl pkgs.zlib ]
=> "/nix/store/9rz8gxhzf8sw4kf2j2f1grr49w8zx5vj-openssl-1.0.1r-dev/bin:/nix/store/wwh7mhwh269sfjkm6k5665b5kgp7jrk2-zlib-1.2.8/bin"

Located at lib/strings.nix:604 in <nixpkgs>.

lib.strings.makeLibraryPath

Construct a library search path (such as RPATH) containing the libraries for a set of packages

Inputs
packages

List of packages

Type
makeLibraryPath :: [Derivation] -> String
Examples
Example 70. lib.strings.makeLibraryPath usage example
makeLibraryPath [ "/usr" "/usr/local" ]
=> "/usr/lib:/usr/local/lib"
pkgs = import <nixpkgs> { }
makeLibraryPath [ pkgs.openssl pkgs.zlib ]
=> "/nix/store/9rz8gxhzf8sw4kf2j2f1grr49w8zx5vj-openssl-1.0.1r/lib:/nix/store/wwh7mhwh269sfjkm6k5665b5kgp7jrk2-zlib-1.2.8/lib"

Located at lib/strings.nix:637 in <nixpkgs>.

lib.strings.makeIncludePath

Construct an include search path (such as C_INCLUDE_PATH) containing the header files for a set of packages or paths.

Inputs
packages

List of packages

Type
makeIncludePath :: [Derivation] -> String
Examples
Example 71. lib.strings.makeIncludePath usage example
makeIncludePath [ "/usr" "/usr/local" ]
=> "/usr/include:/usr/local/include"
pkgs = import <nixpkgs> { }
makeIncludePath [ pkgs.openssl pkgs.zlib ]
=> "/nix/store/9rz8gxhzf8sw4kf2j2f1grr49w8zx5vj-openssl-1.0.1r-dev/include:/nix/store/wwh7mhwh269sfjkm6k5665b5kgp7jrk2-zlib-1.2.8-dev/include"

Located at lib/strings.nix:668 in <nixpkgs>.

lib.strings.makeBinPath

Construct a binary search path (such as $PATH) containing the binaries for a set of packages.

Inputs
packages

List of packages

Type
makeBinPath :: [Derivation] -> String
Examples
Example 72. lib.strings.makeBinPath usage example
makeBinPath ["/root" "/usr" "/usr/local"]
=> "/root/bin:/usr/bin:/usr/local/bin"

Located at lib/strings.nix:696 in <nixpkgs>.

lib.strings.normalizePath

Normalize path, removing extraneous /s

Inputs
s

1. Function argument

Type
normalizePath :: String -> String
Examples
Example 73. lib.strings.normalizePath usage example
normalizePath "/a//b///c/"
=> "/a/b/c/"

Located at lib/strings.nix:723 in <nixpkgs>.

lib.strings.optionalString

Depending on the boolean cond, return either the given string or the empty string. Useful to concatenate against a bigger string.

Inputs
cond

Condition

string

String to return if condition is true

Type
optionalString :: Bool -> String -> String
Examples
Example 74. lib.strings.optionalString usage example
optionalString true "some-string"
=> "some-string"
optionalString false "some-string"
=> ""

Located at lib/strings.nix:766 in <nixpkgs>.

lib.strings.hasPrefix

Determine whether a string has given prefix.

Inputs
pref

Prefix to check for

str

Input string

Type
hasPrefix :: String -> String -> Bool
Examples
Example 75. lib.strings.hasPrefix usage example
hasPrefix "foo" "foobar"
=> true
hasPrefix "foo" "barfoo"
=> false

Located at lib/strings.nix:798 in <nixpkgs>.

lib.strings.hasSuffix

Determine whether a string has given suffix.

Inputs
suffix

Suffix to check for

content

Input string

Type
hasSuffix :: String -> String -> Bool
Examples
Example 76. lib.strings.hasSuffix usage example
hasSuffix "foo" "foobar"
=> false
hasSuffix "foo" "barfoo"
=> true

Located at lib/strings.nix:841 in <nixpkgs>.

lib.strings.hasInfix

Determine whether a string contains the given infix

Inputs
infix

1. Function argument

content

2. Function argument

Type
hasInfix :: String -> String -> Bool
Examples
Example 77. lib.strings.hasInfix usage example
hasInfix "bc" "abcd"
=> true
hasInfix "ab" "abcd"
=> true
hasInfix "cd" "abcd"
=> true
hasInfix "foo" "abcd"
=> false

Located at lib/strings.nix:891 in <nixpkgs>.

lib.strings.stringToCharacters

Convert a string s to a list of characters (i.e. singleton strings). This allows you to, e.g., map a function over each character. However, note that this will likely be horribly inefficient; Nix is not a general purpose programming language. Complex string manipulations should, if appropriate, be done in a derivation. Also note that Nix treats strings as a list of bytes and thus doesn’t handle unicode.

Inputs
s

1. Function argument

Type
stringToCharacters :: String -> [String]
Examples
Example 78. lib.strings.stringToCharacters usage example
stringToCharacters ""
=> [ ]
stringToCharacters "abc"
=> [ "a" "b" "c" ]
stringToCharacters "🦄"
=> [ "�" "�" "�" "�" ]

Located at lib/strings.nix:938 in <nixpkgs>.

lib.strings.stringAsChars

Manipulate a string character by character and replace them by strings before concatenating the results.

Inputs
f

Function to map over each individual character

s

Input string

Type
stringAsChars :: (String -> String) -> String -> String
Examples
Example 79. lib.strings.stringAsChars usage example
stringAsChars (x: if x == "a" then "i" else x) "nax"
=> "nix"

Located at lib/strings.nix:969 in <nixpkgs>.

lib.strings.charToInt

Convert char to ascii value, must be in printable range

Inputs
c

1. Function argument

Type
charToInt :: String -> Int
Examples
Example 80. lib.strings.charToInt usage example
charToInt "A"
=> 65
charToInt "("
=> 40

Located at lib/strings.nix:1003 in <nixpkgs>.

lib.strings.escape

Escape occurrence of the elements of list in string by prefixing it with a backslash.

Inputs
list

1. Function argument

string

2. Function argument

Type
escape :: [String] -> String -> String
Examples
Example 81. lib.strings.escape usage example
escape ["(" ")"] "(foo)"
=> "\\(foo\\)"

Located at lib/strings.nix:1034 in <nixpkgs>.

lib.strings.escapeC

Escape occurrence of the element of list in string by converting to its ASCII value and prefixing it with \x. Only works for printable ascii characters.

Inputs
list

1. Function argument

string

2. Function argument

Type
escapeC :: [String] -> String -> String
Examples
Example 82. lib.strings.escapeC usage example
escapeC [" "] "foo bar"
=> "foo\\x20bar"

Located at lib/strings.nix:1066 in <nixpkgs>.

lib.strings.escapeURL

Escape the string so it can be safely placed inside a URL query.

Inputs
string

1. Function argument

Type
escapeURL :: String -> String
Examples
Example 83. lib.strings.escapeURL usage example
escapeURL "foo/bar baz"
=> "foo%2Fbar%20baz"

Located at lib/strings.nix:1098 in <nixpkgs>.

lib.strings.escapeShellArg

Quote string to be used safely within the Bourne shell if it has any special characters.

Inputs
string

1. Function argument

Type
escapeShellArg :: String -> String
Examples
Example 84. lib.strings.escapeShellArg usage example
escapeShellArg "esc'ape\nme"
=> "'esc'\\''ape\nme'"

Located at lib/strings.nix:1200 in <nixpkgs>.

lib.strings.escapeShellArgs

Quote all arguments that have special characters to be safely passed to the Bourne shell.

Inputs
args

1. Function argument

Type
escapeShellArgs :: [String] -> String
Examples
Example 85. lib.strings.escapeShellArgs usage example
escapeShellArgs ["one" "two three" "four'five"]
=> "one 'two three' 'four'\\''five'"

Located at lib/strings.nix:1236 in <nixpkgs>.

lib.strings.isValidPosixName

Test whether the given name is a valid POSIX shell variable name.

Inputs
name

1. Function argument

Type
isValidPosixName :: String -> Bool
Examples
Example 86. lib.strings.isValidPosixName usage example
isValidPosixName "foo_bar000"
=> true
isValidPosixName "0-bad.jpg"
=> false

Located at lib/strings.nix:1265 in <nixpkgs>.

lib.strings.toShellVar

Translate a Nix value into a shell variable declaration, with proper escaping.

The value can be a string (mapped to a regular variable), a list of strings (mapped to a Bash-style array) or an attribute set of strings (mapped to a Bash-style associative array). Note that “string” includes string-coercible values like paths or derivations.

Strings are translated into POSIX sh-compatible code; lists and attribute sets assume a shell that understands Bash syntax (e.g. Bash or ZSH).

Inputs
name

1. Function argument

value

2. Function argument

Type
toShellVar :: String -> (String | [String] | { [String] :: String }) -> String
Examples
Example 87. lib.strings.toShellVar usage example
''
  ${toShellVar "foo" "some string"}
  [[ "$foo" == "some string" ]]
''

Located at lib/strings.nix:1305 in <nixpkgs>.

lib.strings.toShellVars

Translate an attribute set vars into corresponding shell variable declarations using toShellVar.

Inputs
vars

1. Function argument

Type
toShellVars :: {
  [String] :: String | [String] | { [String] :: String };
} -> String
Examples
Example 88. lib.strings.toShellVars usage example
let
  foo = "value";
  bar = foo;
in ''
  ${toShellVars { inherit foo bar; }}
  [[ "$foo" == "$bar" ]]
''

Located at lib/strings.nix:1351 in <nixpkgs>.

lib.strings.escapeNixString

Turn a string s into a Nix expression representing that string

Inputs
s

1. Function argument

Type
escapeNixString :: String -> String
Examples
Example 89. lib.strings.escapeNixString usage example
escapeNixString "hello\${}\n"
=> "\"hello\\\${}\\n\""

Located at lib/strings.nix:1378 in <nixpkgs>.

lib.strings.escapeRegex

Turn a string s into an exact regular expression

Inputs
s

1. Function argument

Type
escapeRegex :: String -> String
Examples
Example 90. lib.strings.escapeRegex usage example
escapeRegex "[^a-z]*"
=> "\\[\\^a-z]\\*"

Located at lib/strings.nix:1405 in <nixpkgs>.

lib.strings.escapeNixIdentifier

Quotes a string s if it can’t be used as an identifier directly.

Inputs
s

1. Function argument

Type
escapeNixIdentifier :: String -> String
Examples
Example 91. lib.strings.escapeNixIdentifier usage example
escapeNixIdentifier "hello"
=> "hello"
escapeNixIdentifier "0abc"
=> "\"0abc\""

Located at lib/strings.nix:1434 in <nixpkgs>.

lib.strings.escapeXML

Escapes a string s such that it is safe to include verbatim in an XML document.

Inputs
s

1. Function argument

Type
escapeXML :: String -> String
Examples
Example 92. lib.strings.escapeXML usage example
escapeXML ''"test" 'test' < & >''
=> "&quot;test&quot; &apos;test&apos; &lt; &amp; &gt;"

Located at lib/strings.nix:1483 in <nixpkgs>.

lib.strings.toLower

Converts an ASCII string s to lower-case.

Inputs
s

The string to convert to lower-case.

Type
toLower :: String -> String
Examples
Example 93. lib.strings.toLower usage example
toLower "HOME"
=> "home"

Located at lib/strings.nix:1517 in <nixpkgs>.

lib.strings.toUpper

Converts an ASCII string s to upper-case.

Inputs
s

The string to convert to upper-case.

Type
toUpper :: String -> String
Examples
Example 94. lib.strings.toUpper usage example
toUpper "home"
=> "HOME"

Located at lib/strings.nix:1544 in <nixpkgs>.

lib.strings.toSentenceCase

Converts the first character of a string s to upper-case.

Inputs
str

The string to convert to sentence case.

Type
toSentenceCase :: String -> String
Examples
Example 95. lib.strings.toSentenceCase usage example
toSentenceCase "home"
=> "Home"

Located at lib/strings.nix:1571 in <nixpkgs>.

lib.strings.toCamelCase

Converts a string to camelCase. Handles snake_case, PascalCase, kebab-case strings as well as strings delimited by spaces.

Inputs
string

The string to convert to camelCase

Type
toCamelCase :: String -> String
Examples
Example 96. lib.strings.toCamelCase usage example
toCamelCase "hello-world"
=> "helloWorld"
toCamelCase "hello_world"
=> "helloWorld"
toCamelCase "hello world"
=> "helloWorld"
toCamelCase "HelloWorld"
=> "helloWorld"

Located at lib/strings.nix:1615 in <nixpkgs>.

lib.strings.addContextFrom

Appends string context from string like object src to target.

Warning

This is an implementation detail of Nix and should be used carefully.

Strings in Nix carry an invisible context which is a list of strings representing store paths. If the string is later used in a derivation attribute, the derivation will properly populate the inputDrvs and inputSrcs.

Inputs
src

The string to take the context from. If the argument is not a string, it will be implicitly converted to a string.

target

The string to append the context to. If the argument is not a string, it will be implicitly converted to a string.

Type
addContextFrom :: String -> String -> String
Examples
Example 97. lib.strings.addContextFrom usage example
pkgs = import <nixpkgs> { };
addContextFrom pkgs.coreutils "bar"
=> "bar"

The context can be displayed using the toString function:

nix-repl> builtins.getContext (lib.strings.addContextFrom pkgs.coreutils "bar")
{
  "/nix/store/m1s1d2dk2dqqlw3j90jl3cjy2cykbdxz-coreutils-9.5.drv" = { ... };
}

Located at lib/strings.nix:1690 in <nixpkgs>.

lib.strings.splitString

Cut a string with a separator and produces a list of strings which were separated by this separator.

Inputs
sep

1. Function argument

s

2. Function argument

Type
splitString :: String -> String -> [String]
Examples
Example 98. lib.strings.splitString usage example
splitString "." "foo.bar.baz"
=> [ "foo" "bar" "baz" ]
splitString "/" "/usr/local/bin"
=> [ "" "usr" "local" "bin" ]

Located at lib/strings.nix:1723 in <nixpkgs>.

lib.strings.splitStringBy

Splits a string into substrings based on a predicate that examines adjacent characters.

This function provides a flexible way to split strings by checking pairs of characters against a custom predicate function. Unlike simpler splitting functions, this allows for context-aware splitting based on character transitions and patterns.

Inputs
predicate

Function that takes two arguments (previous character and current character) and returns true when the string should be split at the current position. For the first character, previous will be “” (empty string).

keepSplit

Boolean that determines whether the splitting character should be kept as part of the result. If true, the character will be included at the beginning of the next substring; if false, it will be discarded.

str

The input string to split.

Return

A list of substrings from the original string, split according to the predicate.

Type
splitStringBy :: (String -> String -> Bool) -> Bool -> String -> [String]
Examples
Example 99. lib.strings.splitStringBy usage example

Split on periods and hyphens, discarding the separators:

splitStringBy (prev: curr: builtins.elem curr [ "." "-" ]) false "foo.bar-baz"
=> [ "foo" "bar" "baz" ]

Split on transitions from lowercase to uppercase, keeping the uppercase characters:

splitStringBy (prev: curr: builtins.match "[a-z]" prev != null && builtins.match "[A-Z]" curr != null) true "fooBarBaz"
=> [ "foo" "Bar" "Baz" ]

Handle leading separators correctly:

splitStringBy (prev: curr: builtins.elem curr [ "." ]) false ".foo.bar.baz"
=> [ "" "foo" "bar" "baz" ]

Handle trailing separators correctly:

splitStringBy (prev: curr: builtins.elem curr [ "." ]) false "foo.bar.baz."
=> [ "foo" "bar" "baz" "" ]

Located at lib/strings.nix:1793 in <nixpkgs>.

lib.strings.removePrefix

Returns a string without the specified prefix, if the prefix matches.

Inputs
prefix

Prefix to remove if it matches

str

Input string

Type
removePrefix :: String -> String -> String
Examples
Example 100. lib.strings.removePrefix usage example
removePrefix "foo." "foo.bar.baz"
=> "bar.baz"
removePrefix "xxx" "foo.bar.baz"
=> "foo.bar.baz"

Located at lib/strings.nix:1853 in <nixpkgs>.

lib.strings.removeSuffix

Returns a string without the specified suffix, if the suffix matches.

Inputs
suffix

Suffix to remove if it matches

str

Input string

Type
removeSuffix :: String -> String -> String
Examples
Example 101. lib.strings.removeSuffix usage example
removeSuffix "front" "homefront"
=> "home"
removeSuffix "xxx" "homefront"
=> "homefront"

Located at lib/strings.nix:1904 in <nixpkgs>.

lib.strings.versionOlder

Returns true if string v1 denotes a version older than v2.

Inputs
v1

1. Function argument

v2

2. Function argument

Type
versionOlder :: String -> String -> Bool
Examples
Example 102. lib.strings.versionOlder usage example
versionOlder "1.1" "1.2"
=> true
versionOlder "1.1" "1.1"
=> false

Located at lib/strings.nix:1955 in <nixpkgs>.

lib.strings.versionAtLeast

Returns true if string v1 denotes a version equal to or newer than v2.

Inputs
v1

1. Function argument

v2

2. Function argument

Type
versionAtLeast :: String -> String -> Bool
Examples
Example 103. lib.strings.versionAtLeast usage example
versionAtLeast "1.1" "1.0"
=> true
versionAtLeast "1.1" "1.1"
=> true
versionAtLeast "1.1" "1.2"
=> false

Located at lib/strings.nix:1989 in <nixpkgs>.

lib.strings.getName

This function takes an argument x that’s either a derivation or a derivation’s “name” attribute and extracts the name part from that argument.

Inputs
x

1. Function argument

Type
getName :: String | Derivation -> String
Examples
Example 104. lib.strings.getName usage example
getName "youtube-dl-2016.01.01"
=> "youtube-dl"
getName pkgs.youtube-dl
=> "youtube-dl"

Located at lib/strings.nix:2020 in <nixpkgs>.

lib.strings.getVersion

This function takes an argument x that’s either a derivation or a derivation’s “name” attribute and extracts the version part from that argument.

Inputs
x

1. Function argument

Type
getVersion :: String | Derivation -> String
Examples
Example 105. lib.strings.getVersion usage example
getVersion "youtube-dl-2016.01.01"
=> "2016.01.01"
getVersion pkgs.youtube-dl
=> "2016.01.01"

Located at lib/strings.nix:2055 in <nixpkgs>.

lib.strings.nameFromURL

Extract name and version from a URL as shown in the examples.

Separator sep is used to determine the end of the extension.

Inputs
url

1. Function argument

sep

2. Function argument

Type
nameFromURL :: String -> String
Examples
Example 106. lib.strings.nameFromURL usage example
nameFromURL "https://nixos.org/releases/nix/nix-1.7/nix-1.7-x86_64-linux.tar.bz2" "-"
=> "nix"
nameFromURL "https://nixos.org/releases/nix/nix-1.7/nix-1.7-x86_64-linux.tar.bz2" "_"
=> "nix-1.7-x86"

Located at lib/strings.nix:2093 in <nixpkgs>.

lib.strings.cmakeOptionType

Create a "-D<feature>:<type>=<value>" string that can be passed to typical CMake invocations.

Inputs
type

The type of the feature to be set, as described in the CMake set documentation the possible values (case insensitive) are: BOOL FILEPATH PATH STRING INTERNAL LIST

feature

The feature to be set

feature

The feature to be set

value

The desired value

Type
cmakeOptionType :: String -> String -> String -> String
Examples
Example 107. lib.strings.cmakeOptionType usage example
cmakeOptionType "string" "ENGINE" "sdl2"
=> "-DENGINE:STRING=sdl2"

Located at lib/strings.nix:2141 in <nixpkgs>.

lib.strings.cmakeBool

Create a "-D<condition>={TRUE,FALSE}" string that can be passed to typical CMake invocations.

Inputs
condition

The condition to be made true or false

flag

The controlling flag of the condition

Type
cmakeBool :: String -> Bool -> String
Examples
Example 108. lib.strings.cmakeBool usage example
cmakeBool "ENABLE_STATIC_LIBS" false
=> "-DENABLESTATIC_LIBS:BOOL=FALSE"

Located at lib/strings.nix:2187 in <nixpkgs>.

lib.strings.cmakeFeature

Create a "-D<feature>:STRING=<value>" string that can be passed to typical CMake invocations. This is the most typical usage, so it deserves a special case.

Inputs
feature

The feature to be set

value

The desired value

Type
cmakeFeature :: String -> String -> String
Examples
Example 109. lib.strings.cmakeFeature usage example
cmakeFeature "MODULES" "badblock"
=> "-DMODULES:STRING=badblock"

Located at lib/strings.nix:2223 in <nixpkgs>.

lib.strings.mesonOption

Create a "-D<feature>=<value>" string that can be passed to typical Meson invocations.

Inputs
feature

The feature to be set

value

The desired value

Type
mesonOption :: String -> String -> String
Examples
Example 110. lib.strings.mesonOption usage example
mesonOption "engine" "opengl"
=> "-Dengine=opengl"

Located at lib/strings.nix:2258 in <nixpkgs>.

lib.strings.mesonBool

Create a "-D<condition>={true,false}" string that can be passed to typical Meson invocations.

Inputs
condition

The condition to be made true or false

flag

The controlling flag of the condition

Type
mesonBool :: String -> Bool -> String
Examples
Example 111. lib.strings.mesonBool usage example
mesonBool "hardened" true
=> "-Dhardened=true"
mesonBool "static" false
=> "-Dstatic=false"

Located at lib/strings.nix:2295 in <nixpkgs>.

lib.strings.mesonEnable

Create a "-D<feature>={enabled,disabled}" string that can be passed to typical Meson invocations.

Inputs
feature

The feature to be enabled or disabled

flag

The controlling flag

Type
mesonEnable :: String -> Bool -> String
Examples
Example 112. lib.strings.mesonEnable usage example
mesonEnable "docs" true
=> "-Ddocs=enabled"
mesonEnable "savage" false
=> "-Dsavage=disabled"

Located at lib/strings.nix:2332 in <nixpkgs>.

lib.strings.enableFeature

Create an "--{enable,disable}-<feature>" string that can be passed to standard GNU Autoconf scripts.

Inputs
flag

1. Function argument

feature

2. Function argument

Type
enableFeature :: Bool -> String -> String
Examples
Example 113. lib.strings.enableFeature usage example
enableFeature true "shared"
=> "--enable-shared"
enableFeature false "shared"
=> "--disable-shared"

Located at lib/strings.nix:2369 in <nixpkgs>.

lib.strings.enableFeatureAs

Create an "--{enable-<feature>=<value>,disable-<feature>}" string that can be passed to standard GNU Autoconf scripts.

Inputs
flag

1. Function argument

feature

2. Function argument

value

3. Function argument

Type
enableFeatureAs :: Bool -> String -> String -> String
Examples
Example 114. lib.strings.enableFeatureAs usage example
enableFeatureAs true "shared" "foo"
=> "--enable-shared=foo"
enableFeatureAs false "shared" (throw "ignored")
=> "--disable-shared"

Located at lib/strings.nix:2409 in <nixpkgs>.

lib.strings.withFeature

Create an "--{with,without}-<feature>" string that can be passed to standard GNU Autoconf scripts.

Inputs
flag

1. Function argument

feature

2. Function argument

Type
withFeature :: Bool -> String -> String
Examples
Example 115. lib.strings.withFeature usage example
withFeature true "shared"
=> "--with-shared"
withFeature false "shared"
=> "--without-shared"

Located at lib/strings.nix:2444 in <nixpkgs>.

lib.strings.withFeatureAs

Create an "--{with-<feature>=<value>,without-<feature>}" string that can be passed to standard GNU Autoconf scripts.

Inputs
flag

1. Function argument

feature

2. Function argument

value

3. Function argument

Type
withFeatureAs :: Bool -> String -> String -> String
Examples
Example 116. lib.strings.withFeatureAs usage example
withFeatureAs true "shared" "foo"
=> "--with-shared=foo"
withFeatureAs false "shared" (throw "ignored")
=> "--without-shared"

Located at lib/strings.nix:2483 in <nixpkgs>.

lib.strings.fixedWidthString

Create a fixed width string with additional prefix to match required width.

This function will fail if the input string is longer than the requested length.

Inputs
width

1. Function argument

filler

2. Function argument

str

3. Function argument

Type
fixedWidthString :: Int -> String -> String -> String
Examples
Example 117. lib.strings.fixedWidthString usage example
fixedWidthString 5 "0" (toString 15)
=> "00015"

Located at lib/strings.nix:2522 in <nixpkgs>.

lib.strings.fixedWidthNumber

Format a number adding leading zeroes up to fixed width.

Inputs
width

1. Function argument

n

2. Function argument

Type
fixedWidthNumber :: Int -> Int -> String
Examples
Example 118. lib.strings.fixedWidthNumber usage example
fixedWidthNumber 5 15
=> "00015"

Located at lib/strings.nix:2560 in <nixpkgs>.

lib.strings.floatToString

Convert a float to a string, but emit a warning when precision is lost during the conversion

Inputs
float

1. Function argument

Type
floatToString :: Float -> String
Examples
Example 119. lib.strings.floatToString usage example
floatToString 0.000001
=> "0.000001"
floatToString 0.0000001
=> trace: warning: Imprecise conversion from float to string 0.000000
   "0.000000"

Located at lib/strings.nix:2591 in <nixpkgs>.

lib.strings.isConvertibleWithToString

Check whether a list or other value x can be passed to toString.

Many types of value are coercible to string this way, including int, float, null, bool, list of similarly coercible values.

Inputs
val

1. Function argument

Type
isConvertibleWithToString :: Any -> Bool

Located at lib/strings.nix:2616 in <nixpkgs>.

lib.strings.isStringLike

Check whether a value can be coerced to a string. The value must be a string, path, or attribute set.

String-like values can be used without explicit conversion in string interpolations and in most functions that expect a string.

Inputs
x

1. Function argument

Type
isStringLike :: Any -> Bool

Located at lib/strings.nix:2645 in <nixpkgs>.

lib.strings.isStorePath

Check whether a value x is a store path.

Inputs
x

1. Function argument

Type
isStorePath :: Any -> Bool
Examples
Example 120. lib.strings.isStorePath usage example
isStorePath "/nix/store/d945ibfx9x185xf04b890y4f9g3cbb63-python-2.7.11/bin/python"
=> false
isStorePath "/nix/store/d945ibfx9x185xf04b890y4f9g3cbb63-python-2.7.11"
=> true
isStorePath pkgs.python
=> true
isStorePath [] || isStorePath 42 || isStorePath {} || …
=> false

Located at lib/strings.nix:2678 in <nixpkgs>.

lib.strings.toInt

Parse a string as an int. Does not support parsing of integers with preceding zero due to ambiguity between zero-padded and octal numbers. See toIntBase10.

Inputs
str

A string to be interpreted as an int.

Type
toInt :: String -> Int
Examples
Example 121. lib.strings.toInt usage example
toInt "1337"
=> 1337

toInt "-4"
=> -4

toInt " 123 "
=> 123

toInt "00024"
=> error: Ambiguity in interpretation of 00024 between octal and zero padded integer.

toInt "3.14"
=> error: floating point JSON numbers are not supported

Located at lib/strings.nix:2735 in <nixpkgs>.

lib.strings.toIntBase10

Parse a string as a base 10 int. This supports parsing of zero-padded integers.

Inputs
str

A string to be interpreted as an int.

Type
toIntBase10 :: String -> Int
Examples
Example 122. lib.strings.toIntBase10 usage example
toIntBase10 "1337"
=> 1337

toIntBase10 "-4"
=> -4

toIntBase10 " 123 "
=> 123

toIntBase10 "00024"
=> 24

toIntBase10 "3.14"
=> error: floating point JSON numbers are not supported

Located at lib/strings.nix:2805 in <nixpkgs>.

lib.strings.fileContents

Read the contents of a file removing the trailing \n

Inputs
file

1. Function argument

Type
fileContents :: Path -> String
Examples
Example 123. lib.strings.fileContents usage example
$ echo "1.0" > ./version

fileContents ./version
=> "1.0"

Located at lib/strings.nix:2866 in <nixpkgs>.

lib.strings.sanitizeDerivationName

Creates a valid derivation name from a potentially invalid one.

Inputs
string

1. Function argument

Type
sanitizeDerivationName :: String -> String
Examples
Example 124. lib.strings.sanitizeDerivationName usage example
sanitizeDerivationName "../hello.bar # foo"
=> "-hello.bar-foo"
sanitizeDerivationName ""
=> "unknown"
sanitizeDerivationName pkgs.hello
=> "-nix-store-2g75chlbpxlrqn15zlby2dfh8hr9qwbk-hello-2.10"

Located at lib/strings.nix:2897 in <nixpkgs>.

lib.strings.levenshtein

Computes the Levenshtein distance between two strings a and b.

Complexity O(n*m) where n and m are the lengths of the strings. Algorithm adjusted from this stackoverflow comment

Inputs
a

1. Function argument

b

2. Function argument

Type
levenshtein :: String -> String -> Int
Examples
Example 125. lib.strings.levenshtein usage example
levenshtein "foo" "foo"
=> 0
levenshtein "book" "hook"
=> 1
levenshtein "hello" "Heyo"
=> 3

Located at lib/strings.nix:2959 in <nixpkgs>.

lib.strings.commonPrefixLength

Returns the length of the prefix that appears in both strings a and b.

Inputs
a

1. Function argument

b

2. Function argument

Type
commonPrefixLength :: String -> String -> Int

Located at lib/strings.nix:2996 in <nixpkgs>.

lib.strings.commonSuffixLength

Returns the length of the suffix common to both strings a and b.

Inputs
a

1. Function argument

b

2. Function argument

Type
commonSuffixLength :: String -> String -> Int

Located at lib/strings.nix:3028 in <nixpkgs>.

lib.strings.levenshteinAtMost

Returns whether the levenshtein distance between two strings a and b is at most some value k.

Complexity is O(min(n,m)) for k <= 2 and O(n*m) otherwise

Inputs
k

Distance threshold

a

String a

b

String b

Type
levenshteinAtMost :: Int -> String -> String -> Bool
Examples
Example 126. lib.strings.levenshteinAtMost usage example
levenshteinAtMost 0 "foo" "foo"
=> true
levenshteinAtMost 1 "foo" "boa"
=> false
levenshteinAtMost 2 "foo" "boa"
=> true
levenshteinAtMost 2 "This is a sentence" "this is a sentense."
=> false
levenshteinAtMost 3 "This is a sentence" "this is a sentense."
=> true

Located at lib/strings.nix:3084 in <nixpkgs>.

lib.versions: version string functions

lib.versions.splitVersion

Break a version string into its component parts.

Type
splitVersion :: String -> [String]
Examples
Example 127. splitVersion usage example
splitVersion "1.2.3"
=> ["1" "2" "3"]

Located at lib/versions.nix:28 in <nixpkgs>.

lib.versions.major

Get the major version string from a string.

Inputs
v

1. Function argument

Type
major :: String -> String
Examples
Example 128. major usage example
major "1.2.3"
=> "1"

Located at lib/versions.nix:56 in <nixpkgs>.

lib.versions.minor

Get the minor version string from a string.

Inputs
v

1. Function argument

Type
minor :: String -> String
Examples
Example 129. minor usage example
minor "1.2.3"
=> "2"

Located at lib/versions.nix:84 in <nixpkgs>.

lib.versions.patch

Get the patch version string from a string.

Inputs
v

1. Function argument

Type
patch :: String -> String
Examples
Example 130. patch usage example
patch "1.2.3"
=> "3"

Located at lib/versions.nix:112 in <nixpkgs>.

lib.versions.majorMinor

Get string of the first two parts (major and minor) of a version string.

Inputs
v

1. Function argument

Type
majorMinor :: String -> String
Examples
Example 131. majorMinor usage example
majorMinor "1.2.3"
=> "1.2"

Located at lib/versions.nix:141 in <nixpkgs>.

lib.versions.pad

Pad a version string with zeros to match the given number of components.

Inputs
n

1. Function argument

version

2. Function argument

Type
pad :: Int -> String -> String
Examples
Example 132. pad usage example
pad 3 "1.2"
=> "1.2.0"
pad 3 "1.3-rc1"
=> "1.3.0-rc1"
pad 3 "1.2.3.4"
=> "1.2.3"

Located at lib/versions.nix:177 in <nixpkgs>.

lib.trivial: miscellaneous functions

lib.trivial.id

The identity function For when you need a function that does “nothing”.

Inputs
x

The value to return

Type
id :: a -> a

Located at lib/trivial.nix:63 in <nixpkgs>.

lib.trivial.const

The constant function

Ignores the second argument. If called with only one argument, constructs a function that always returns a static value.

Inputs
x

Value to return

y

Value to ignore

Type
const :: a -> b -> a
Examples
Example 133. lib.trivial.const usage example
let f = const 5; in f 10
=> 5

Located at lib/trivial.nix:98 in <nixpkgs>.

lib.trivial.pipe

Pipes a value through a list of functions, left to right.

Inputs
value

Value to start piping.

fns

List of functions to apply sequentially.

Type
pipe :: a -> [(a -> b) (b -> c) ... (x -> y) (y -> z)] -> z
Examples
Example 134. lib.trivial.pipe usage example
pipe 2 [
    (x: x + 2)  # 2 + 2 = 4
    (x: x * 2)  # 4 * 2 = 8
  ]
=> 8

# ideal to do text transformations
pipe [ "a/b" "a/c" ] [

  # create the cp command
  (map (file: ''cp "${src}/${file}" $out\n''))

  # concatenate all commands into one string
  lib.concatStrings

  # make that string into a nix derivation
  (pkgs.runCommand "copy-to-out" {})

]
=> <drv which copies all files to $out>

The output type of each function has to be the input type
of the next function, and the last function returns the
final value.

Located at lib/trivial.nix:152 in <nixpkgs>.

lib.trivial.concat

Concatenate two lists

Inputs
x

1. Function argument

y

2. Function argument

Type
concat :: [a] -> [a] -> [a]
Examples
Example 135. lib.trivial.concat usage example
concat [ 1 2 ] [ 3 4 ]
=> [ 1 2 3 4 ]

Located at lib/trivial.nix:191 in <nixpkgs>.

lib.trivial."or" {#function-library-lib.trivial.“or”}

boolean “or”

Inputs
x

1. Function argument

y

2. Function argument

Type
or :: Bool -> Bool -> Bool

lib.trivial.and

boolean “and”

Inputs
x

1. Function argument

y

2. Function argument

Type
and :: Bool -> Bool -> Bool

Located at lib/trivial.nix:233 in <nixpkgs>.

lib.trivial.xor

boolean “exclusive or”

Inputs
x

1. Function argument

y

2. Function argument

Type
xor :: bool -> bool -> bool

Located at lib/trivial.nix:256 in <nixpkgs>.

lib.trivial.bitNot

bitwise “not”

Type
bitNot :: Number -> Number

Located at lib/trivial.nix:267 in <nixpkgs>.

lib.trivial.boolToString

Convert a boolean to a string.

This function uses the strings “true” and “false” to represent boolean values. Calling toString on a bool instead returns “1” and “” (sic!).

Inputs
b

1. Function argument

Type
boolToString :: Bool -> String

Located at lib/trivial.nix:288 in <nixpkgs>.

lib.trivial.boolToYesNo

Converts a boolean to a string.

This function uses the strings “yes” and “no” to represent boolean values.

Inputs
b

The boolean to convert

Type
boolToYesNo :: Bool -> String

Located at lib/trivial.nix:308 in <nixpkgs>.

lib.trivial.mergeAttrs

Merge two attribute sets shallowly, right side trumps left

Inputs
x

Left attribute set

y

Right attribute set (higher precedence for equal keys)

Type
mergeAttrs :: AttrSet -> AttrSet -> AttrSet
Examples
Example 136. lib.trivial.mergeAttrs usage example
mergeAttrs { a = 1; b = 2; } { b = 3; c = 4; }
=> { a = 1; b = 3; c = 4; }

Located at lib/trivial.nix:340 in <nixpkgs>.

lib.trivial.flip

Flip the order of the arguments of a binary function.

Inputs
f

1. Function argument

a

2. Function argument

b

3. Function argument

Type
flip :: (a -> b -> c) -> (b -> a -> c)
Examples
Example 137. lib.trivial.flip usage example
flip concat [1] [2]
=> [ 2 1 ]

Located at lib/trivial.nix:376 in <nixpkgs>.

lib.trivial.defaultTo

Returns maybeValue if not null, otherwise return default.

Inputs
default

1. Function argument

maybeValue

2. Function argument

Type
defaultTo :: a -> (b | Null) -> (b | a)
Examples
Example 138. lib.trivial.defaultTo usage example
defaultTo "default" null
=> "default"
defaultTo "default" "foo"
=> "foo"
defaultTo "default" false
=> false

Located at lib/trivial.nix:414 in <nixpkgs>.

lib.trivial.mapNullable

Apply function if the supplied argument is non-null.

Inputs
f

Function to call

a

Argument to check for null before passing it to f

Type
mapNullable :: (a -> b) -> (a | Null) -> (b | Null)
Examples
Example 139. lib.trivial.mapNullable usage example
mapNullable (x: x+1) null
=> null
mapNullable (x: x+1) 22
=> 23

Located at lib/trivial.nix:448 in <nixpkgs>.

lib.trivial.version

Returns the current full nixpkgs version number.

Located at lib/trivial.nix:455 in <nixpkgs>.

lib.trivial.release

Returns the current nixpkgs release number as string.

Located at lib/trivial.nix:460 in <nixpkgs>.

lib.trivial.oldestSupportedRelease

The latest release that is supported, at the time of release branch-off, if applicable.

Ideally, out-of-tree modules should be able to evaluate cleanly with all supported Nixpkgs versions (master, release and old release until EOL). So if possible, deprecation warnings should take effect only when all out-of-tree expressions/libs/modules can upgrade to the new way without losing support for supported Nixpkgs versions.

This release number allows deprecation warnings to be implemented such that they take effect as soon as the oldest release reaches end of life.

Located at lib/trivial.nix:475 in <nixpkgs>.

lib.trivial.isInOldestRelease

Whether a feature is supported in all supported releases (at the time of release branch-off, if applicable). See oldestSupportedRelease.

Inputs
release

Release number of feature introduction as an integer, e.g. 2111 for 21.11. Set it to the upcoming release, matching the nixpkgs/.version file.

Located at lib/trivial.nix:490 in <nixpkgs>.

lib.trivial.oldestSupportedReleaseIsAtLeast

Alias for isInOldestRelease introduced in 24.11. Use isInOldestRelease in expressions outside of Nixpkgs for greater compatibility.

Located at lib/trivial.nix:499 in <nixpkgs>.

lib.trivial.codeName

Returns the current nixpkgs release code name.

On each release the first letter is bumped and a new animal is chosen starting with that new letter.

Located at lib/trivial.nix:507 in <nixpkgs>.

lib.trivial.versionSuffix

Returns the current nixpkgs version suffix as string.

Located at lib/trivial.nix:512 in <nixpkgs>.

lib.trivial.revisionWithDefault

Attempts to return the the current revision of nixpkgs and returns the supplied default value otherwise.

Inputs
default

Default value to return if revision can not be determined

Type
revisionWithDefault :: String -> String

Located at lib/trivial.nix:534 in <nixpkgs>.

lib.trivial.inNixShell

Determine whether the function is being called from inside a Nix shell.

Type
inNixShell :: Bool

Located at lib/trivial.nix:559 in <nixpkgs>.

lib.trivial.inPureEvalMode

Determine whether the function is being called from inside pure-eval mode by seeing whether builtins contains currentSystem. If not, we must be in pure-eval mode.

Type
inPureEvalMode :: Bool

Located at lib/trivial.nix:572 in <nixpkgs>.

lib.trivial.min

Returns minimum of two numbers.

Inputs
x

1. Function argument

y

2. Function argument

Type
min :: Number -> Number -> Number

Located at lib/trivial.nix:595 in <nixpkgs>.

lib.trivial.max

Returns maximum of two numbers.

Inputs
x

1. Function argument

y

2. Function argument

Type
max :: Number -> Number -> Number

Located at lib/trivial.nix:616 in <nixpkgs>.

lib.trivial.mod

Integer modulus

Inputs
base

1. Function argument

int

2. Function argument

Type
mod :: Int -> Int -> Int
Examples
Example 140. lib.trivial.mod usage example
mod 11 10
=> 1
mod 1 10
=> 1

Located at lib/trivial.nix:650 in <nixpkgs>.

lib.trivial.compare

C-style comparisons

a < b, compare a b => -1 a == b, compare a b => 0 a > b, compare a b => 1

Inputs
a

1. Function argument

b

2. Function argument

Type
compare :: a -> a -> Int

Located at lib/trivial.nix:677 in <nixpkgs>.

lib.trivial.splitByAndCompare

Split type into two subtypes by predicate p, take all elements of the first subtype to be less than all the elements of the second subtype, compare elements of a single subtype with yes and no respectively.

Inputs
p

Predicate

yes

Comparison function if predicate holds for both values

no

Comparison function if predicate holds for neither value

a

First value to compare

b

Second value to compare

Type
splitByAndCompare :: (a -> Bool) -> (a -> a -> Int) -> (a -> a -> Int) -> (a -> a -> Int)
Examples
Example 141. lib.trivial.splitByAndCompare usage example
let cmp = splitByAndCompare (hasPrefix "foo") compare compare; in

cmp "a" "z" => -1
cmp "fooa" "fooz" => -1

cmp "f" "a" => 1
cmp "fooa" "a" => -1
# while
compare "fooa" "a" => 1

Located at lib/trivial.nix:738 in <nixpkgs>.

lib.trivial.importJSON

Reads a JSON file.

Examples
Example 142. lib.trivial.importJSON usage example

example.json

{
  "title": "Example JSON",
  "hello": {
    "world": "foo",
    "bar": {
      "foobar": true
    }
  }
}
importJSON ./example.json
=> {
  title = "Example JSON";
  hello = {
    world = "foo";
    bar = {
      foobar = true;
    };
  };
}

Inputs
path

1. Function argument

Type
importJSON :: Path -> Any

Located at lib/trivial.nix:794 in <nixpkgs>.

lib.trivial.importTOML

Reads a TOML file.

Examples
Example 143. lib.trivial.importTOML usage example

example.toml

title = "TOML Example"

[hello]
world = "foo"

[hello.bar]
foobar = true
importTOML ./example.toml
=> {
  title = "TOML Example";
  hello = {
    world = "foo";
    bar = {
      foobar = true;
    };
  };
}

Inputs
path

1. Function argument

Type
importTOML :: Path -> Any

Located at lib/trivial.nix:841 in <nixpkgs>.

lib.trivial.warn

warn message value

Print a warning before returning the second argument.

See builtins.warn (Nix >= 2.23). On older versions, the Nix 2.23 behavior is emulated with builtins.trace, including the NIX_ABORT_ON_WARN behavior, but not the nix.conf setting or command line option.

Inputs
message (String)

Warning message to print before evaluating value.

value (any value)

Value to return as-is.

Type
warn :: String -> a -> a

Located at lib/trivial.nix:867 in <nixpkgs>.

lib.trivial.warnIf

warnIf condition message value

Like warn, but only warn when the first argument is true.

Inputs
condition (Boolean)

true to trigger the warning before continuing with value.

message (String)

Warning message to print before evaluating

value (any value)

Value to return as-is.

Type
warnIf :: Bool -> String -> a -> a

Located at lib/trivial.nix:914 in <nixpkgs>.

lib.trivial.warnIfNot

warnIfNot condition message value

Like warnIf, but negated: warn if the first argument is false.

Inputs
condition

false to trigger the warning before continuing with val.

message

Warning message to print before evaluating value.

value

Value to return as-is.

Type
warnIfNot :: Bool -> String -> a -> a

Located at lib/trivial.nix:941 in <nixpkgs>.

lib.trivial.throwIfNot

Like the assert b; e expression, but with a custom error message and without the semicolon.

If true, return the identity function, r: r.

If false, throw the error message.

Calls can be juxtaposed using function application, as (r: r) a = a, so (r: r) (r: r) a = a, and so forth.

Inputs
cond

1. Function argument

msg

2. Function argument

Type
throwIfNot :: Bool -> String -> a -> (a | Never)
Examples
Example 144. lib.trivial.throwIfNot usage example
throwIfNot (lib.isList overlays) "The overlays argument to nixpkgs must be a list."
lib.foldr (x: throwIfNot (lib.isFunction x) "All overlays passed to nixpkgs must be functions.") (r: r) overlays
pkgs

Located at lib/trivial.nix:982 in <nixpkgs>.

lib.trivial.throwIf

Like throwIfNot, but negated (throw if the first argument is true).

Inputs
cond

1. Function argument

msg

2. Function argument

Type
throwIf :: Bool -> String -> a -> (a | Never)

Located at lib/trivial.nix:1003 in <nixpkgs>.

lib.trivial.checkListOfEnum

Check if the elements in a list are valid values from a enum, returning the identity function, or throwing an error message otherwise.

Inputs
msg

1. Function argument

valid

2. Function argument

given

3. Function argument

Type
checkListOfEnum :: String -> [a] -> [a] -> ((b -> b) | Never)
Examples
Example 145. lib.trivial.checkListOfEnum usage example
let colorVariants = ["bright" "dark" "black"]
in checkListOfEnum "color variants" [ "standard" "light" "dark" ] colorVariants;
=>
error: color variants: bright, black unexpected; valid ones: standard, light, dark

Located at lib/trivial.nix:1041 in <nixpkgs>.

lib.trivial.setFunctionArgs

Add metadata about expected function arguments to a function. The metadata should match the format given by builtins.functionArgs, i.e. a set from expected argument to a bool representing whether that argument has a default or not.

This function is necessary because you can’t dynamically create a function of the { a, b ? foo, ... }: format, but some facilities like callPackage expect to be able to query expected arguments.

Inputs
f

1. Function argument

args

2. Function argument

Type
setFunctionArgs : (a -> b) -> { [String] :: Bool } -> (a -> b)

Located at lib/trivial.nix:1081 in <nixpkgs>.

lib.trivial.functionArgs

Extract the expected function arguments from a function. This works both with nix-native { a, b ? foo, ... }: style functions and functions with args set with setFunctionArgs. It has the same return type and semantics as builtins.functionArgs.

Inputs
f

1. Function argument

Type
functionArgs : (a -> b) -> { [String] :: Bool }

Located at lib/trivial.nix:1105 in <nixpkgs>.

lib.trivial.isFunction

Check whether something is a function or something annotated with function args.

Inputs
f

1. Function argument

Type
isFunction : Any -> Bool

Located at lib/trivial.nix:1127 in <nixpkgs>.

lib.trivial.mirrorFunctionArgs

mirrorFunctionArgs f g creates a new function g' with the same behavior as g (g' x == g x) but its function arguments mirroring f (lib.functionArgs g' == lib.functionArgs f).

Inputs
f

Function to provide the argument metadata

g

Function to set the argument metadata to

Type
mirrorFunctionArgs :: (a -> b) -> (a -> c) -> (a -> c)
Examples
Example 146. lib.trivial.mirrorFunctionArgs usage example
addab = {a, b}: a + b
addab { a = 2; b = 4; }
=> 6
lib.functionArgs addab
=> { a = false; b = false; }
addab1 = attrs: addab attrs + 1
addab1 { a = 2; b = 4; }
=> 7
lib.functionArgs addab1
=> { }
addab1' = lib.mirrorFunctionArgs addab addab1
addab1' { a = 2; b = 4; }
=> 7
lib.functionArgs addab1'
=> { a = false; b = false; }

Located at lib/trivial.nix:1177 in <nixpkgs>.

lib.trivial.toFunction

Turns any non-callable values into constant functions. Returns callable values as is.

Inputs
v

Any value

Examples
Example 147. lib.trivial.toFunction usage example
nix-repl> lib.toFunction 1 2
1

nix-repl> lib.toFunction (x: x + 1) 2
3

Located at lib/trivial.nix:1211 in <nixpkgs>.

lib.trivial.fromHexString

Convert a hexadecimal string to it’s integer representation.

Type
fromHexString :: String -> Int
Examples
Example 148. lib.trivial.fromHexString usage examples
fromHexString "FF"
=> 255

fromHexString "0x7fffffffffffffff"
=> 9223372036854775807

Located at lib/trivial.nix:1234 in <nixpkgs>.

lib.trivial.toHexString

Convert the given positive integer to a string of its hexadecimal representation.

Type
toHexString :: Int -> String
Examples
Example 149. lib.trivial.toHexString usage example
toHexString 0 => "0"

toHexString 16 => "10"

toHexString 250 => "FA"

Located at lib/trivial.nix:1274 in <nixpkgs>.

lib.trivial.toBaseDigits

toBaseDigits base i converts the positive integer i to a list of its digits in the given base.

Inputs
base

1. Function argument

i

2. Function argument

Type
toBaseDigits :: Int -> Int -> [Int]
Examples
Example 150. lib.trivial.toBaseDigits
toBaseDigits 10 123 => [ 1 2 3 ]

toBaseDigits 2 6 => [ 1 1 0 ]

toBaseDigits 16 250 => [ 15 10 ]

Located at lib/trivial.nix:1321 in <nixpkgs>.

lib.fixedPoints: explicit recursion functions

lib.fixedPoints.fix

fix f computes the fixed point of the given function f. In other words, the return value is x in x = f x.

f must be a lazy function. This means that x must be a value that can be partially evaluated, such as an attribute set, a list, or a function. This way, f can use one part of x to compute another part.

Relation to syntactic recursion

This section explains fix by refactoring from syntactic recursion to a call of fix instead.

For context, Nix lets you define attributes in terms of other attributes syntactically using the rec { } syntax.

nix-repl> rec {
  foo = "foo";
  bar = "bar";
  foobar = foo + bar;
}
{ bar = "bar"; foo = "foo"; foobar = "foobar"; }

This is convenient when constructing a value to pass to a function for example, but an equivalent effect can be achieved with the let binding syntax:

nix-repl> let self = {
  foo = "foo";
  bar = "bar";
  foobar = self.foo + self.bar;
}; in self
{ bar = "bar"; foo = "foo"; foobar = "foobar"; }

But in general you can get more reuse out of let bindings by refactoring them to a function.

nix-repl> f = self: {
  foo = "foo";
  bar = "bar";
  foobar = self.foo + self.bar;
}

This is where fix comes in, it contains the syntactic recursion that’s not in f anymore.

nix-repl> fix = f:
  let self = f self; in self;

By applying fix we get the final result.

nix-repl> fix f
{ bar = "bar"; foo = "foo"; foobar = "foobar"; }

Such a refactored f using fix is not useful by itself. See extends for an example use case. There self is also often called final.

Inputs
f

1. Function argument

Type
fix :: (a -> a) -> a
Examples
Example 151. lib.fixedPoints.fix usage example
fix (self: { foo = "foo"; bar = "bar"; foobar = self.foo + self.bar; })
=> { bar = "bar"; foo = "foo"; foobar = "foobar"; }

fix (self: [ 1 2 (elemAt self 0 + elemAt self 1) ])
=> [ 1 2 3 ]

Located at lib/fixed-points.nix:92 in <nixpkgs>.

lib.fixedPoints.fix'

A variant of fix that records the original recursive attribute set in the result, in an attribute named __unfix__.

This is useful in combination with the extends function to implement deep overriding.

Inputs
f

1. Function argument

Type
fix' :: (a -> a) -> a

Located at lib/fixed-points.nix:118 in <nixpkgs>.

lib.fixedPoints.converge

Returns the fixpoint that f converges to when called iteratively, starting with the input x.

nix-repl> converge (x: x / 2) 16
0
Inputs
f

1. Function argument

x

2. Function argument

Type
converge :: (a -> a) -> a -> a

Located at lib/fixed-points.nix:152 in <nixpkgs>.

lib.fixedPoints.extends

Extend a function using an overlay.

Overlays allow modifying and extending fixed-point functions, specifically ones returning attribute sets. A fixed-point function is a function which is intended to be evaluated by passing the result of itself as the argument. This is possible due to Nix’s lazy evaluation.

A fixed-point function returning an attribute set has the form

final: {
  # attributes
}

where final refers to the lazily evaluated attribute set returned by the fixed-point function.

An overlay to such a fixed-point function has the form

final: prev: {
  # attributes
}

where prev refers to the result of the original function to final, and final is the result of the composition of the overlay and the original function.

Applying an overlay is done with extends:

let
  f = final: {
    # attributes
  };
  overlay = final: prev: {
    # attributes
  };
in extends overlay f;

To get the value of final, use lib.fix:

let
  f = final: {
    # attributes
  };
  overlay = final: prev: {
    # attributes
  };
  g = extends overlay f;
in fix g

Note

The argument to the given fixed-point function after applying an overlay will not refer to its own return value, but rather to the value after evaluating the overlay function.

The given fixed-point function is called with a separate argument than if it was evaluated with lib.fix.

Example 152. Extend a fixed-point function with an overlay

Define a fixed-point function f that expects its own output as the argument final:

f = final: {
  # Constant value a
  a = 1;

  # b depends on the final value of a, available as final.a
  b = final.a + 2;
}

Evaluate this using lib.fix to get the final result:

fix f
=> { a = 1; b = 3; }

An overlay represents a modification or extension of such a fixed-point function. Here’s an example of an overlay:

overlay = final: prev: {
  # Modify the previous value of a, available as prev.a
  a = prev.a + 10;

  # Extend the attribute set with c, letting it depend on the final values of a and b
  c = final.a + final.b;
}

Use extends overlay f to apply the overlay to the fixed-point function f. This produces a new fixed-point function g with the combined behavior of f and overlay:

g = extends overlay f

The result is a function, so we can’t print it directly, but it’s the same as:

g' = final: {
  # The constant from f, but changed with the overlay
  a = 1 + 10;

  # Unchanged from f
  b = final.a + 2;

  # Extended in the overlay
  c = final.a + final.b;
}

Evaluate this using lib.fix again to get the final result:

fix g
=> { a = 11; b = 13; c = 24; }

Inputs
overlay

The overlay to apply to the fixed-point function

f

The fixed-point function

Type
extends :: (AttrSet -> AttrSet -> AttrSet) # The overlay to apply to the fixed-point function
        -> (AttrSet -> AttrSet) # A fixed-point function
        -> (AttrSet -> AttrSet) # The resulting fixed-point function
Examples
Example 153. lib.fixedPoints.extends usage example
f = final: { a = 1; b = final.a + 2; }

fix f
=> { a = 1; b = 3; }

fix (extends (final: prev: { a = prev.a + 10; }) f)
=> { a = 11; b = 13; }

fix (extends (final: prev: { b = final.a + 5; }) f)
=> { a = 1; b = 6; }

fix (extends (final: prev: { c = final.a + final.b; }) f)
=> { a = 1; b = 3; c = 4; }

Located at lib/fixed-points.nix:325 in <nixpkgs>.

lib.fixedPoints.composeExtensions

Compose two overlay functions and return a single overlay function that combines them. For more details see: composeManyExtensions.

Located at lib/fixed-points.nix:340 in <nixpkgs>.

lib.fixedPoints.composeManyExtensions

Composes a list of overlays and returns a single overlay function that combines them.

Note

The result is produced by using the update operator //. This means nested values of previous overlays are not merged recursively. In other words, previously defined attributes are replaced, ignoring the previous value, unless referenced by the overlay; for example final: prev: { foo = final.foo + 1; }.

Inputs
extensions

A list of overlay functions

Note

The order of the overlays in the list is important.

Each overlay function takes two arguments, by convention final and prev, and returns an attribute set.

  • final is the result of the fixed-point function, with all overlays applied.

  • prev is the result of the previous overlay function(s).

Type
# Pseudo code
let
  #               final      prev
  #                 ↓          ↓
  OverlayFn = { ... } -> { ... } -> { ... };
in
composeManyExtensions :: [OverlayFn] -> OverlayFn
Examples
Example 154. lib.fixedPoints.composeManyExtensions usage example
let
  # The "original function" that is extended by the overlays.
  # Note that it doesn't have prev: as argument since no overlay function precedes it.
  original = final: { a = 1; };

  # Each overlay function has 'final' and 'prev' as arguments.
  overlayA = final: prev: { b = final.c; c = 3; };
  overlayB = final: prev: { c = 10; x = prev.c or 5; };

  extensions = composeManyExtensions [ overlayA overlayB ];

  # Calculate the fixed point of all composed overlays.
  fixedpoint = lib.fix (lib.extends extensions original );

in fixedpoint
=>
{
  a = 1;
  b = 10;
  c = 10;
  x = 3;
}

Located at lib/fixed-points.nix:412 in <nixpkgs>.

lib.fixedPoints.makeExtensible

Create an overridable, recursive attribute set. For example:

nix-repl> obj = makeExtensible (final: { })

nix-repl> obj
{ __unfix__ = «lambda»; extend = «lambda»; }

nix-repl> obj = obj.extend (final: prev: { foo = "foo"; })

nix-repl> obj
{ __unfix__ = «lambda»; extend = «lambda»; foo = "foo"; }

nix-repl> obj = obj.extend (final: prev: { foo = prev.foo + " + "; bar = "bar"; foobar = final.foo + final.bar; })

nix-repl> obj
{ __unfix__ = «lambda»; bar = "bar"; extend = «lambda»; foo = "foo + "; foobar = "foo + bar"; }

Located at lib/fixed-points.nix:434 in <nixpkgs>.

lib.fixedPoints.makeExtensibleWithCustomName

Same as makeExtensible but the name of the extending attribute is customized.

Inputs
extenderName

1. Function argument

rattrs

2. Function argument

Located at lib/fixed-points.nix:450 in <nixpkgs>.

lib.fixedPoints.toExtension

Convert to an extending function (overlay).

toExtension is the toFunction for extending functions (a.k.a. extensions or overlays). It converts a non-function or a single-argument function to an extending function, while returning a two-argument function as-is.

That is, it takes a value of the shape x, prev: x, or final: prev: x, and returns final: prev: x, assuming x is not a function.

This function takes care of the input to stdenv.mkDerivation’s overrideAttrs function. It bridges the gap between <pkg>.overrideAttrs before and after the overlay-style support.

Inputs
f

The function or value to convert to an extending function.

Type
toExtension :: b' -> Any -> Any -> b'
or
toExtension :: (a -> b') -> Any -> a -> b'
or
toExtension :: (a -> a -> b) -> a -> a -> b
where b' = ! Callable

Set a = b = b' = AttrSet & ! Callable to make toExtension return an extending function.
Examples
Example 155. lib.fixedPoints.toExtension usage example
fix (final: { a = 0; c = final.a; })
=> { a = 0; c = 0; };

fix (extends (toExtension { a = 1; b = 2; }) (final: { a = 0; c = final.a; }))
=> { a = 1; b = 2; c = 1; };

fix (extends (toExtension (prev: { a = 1; b = prev.a; })) (final: { a = 0; c = final.a; }))
=> { a = 1; b = 0; c = 1; };

fix (extends (toExtension (final: prev: { a = 1; b = prev.a; c = final.a + 1 })) (final: { a = 0; c = final.a; }))
=> { a = 1; b = 0; c = 2; };

Located at lib/fixed-points.nix:512 in <nixpkgs>.

lib.lists: list manipulation functions

General list operations.

lib.lists.singleton

Create a list consisting of a single element. singleton x is sometimes more convenient with respect to indentation than [x] when x spans multiple lines.

Inputs
x

1. Function argument

Type
singleton :: a -> [a]
Examples
Example 156. lib.lists.singleton usage example
singleton "foo"
=> [ "foo" ]

Located at lib/lists.nix:59 in <nixpkgs>.

lib.lists.forEach

Apply the function to each element in the list. Same as map, but arguments flipped.

Inputs
xs

1. Function argument

f

2. Function argument

Type
forEach :: [a] -> (a -> b) -> [b]
Examples
Example 157. lib.lists.forEach usage example
forEach [ 1 2 ] (x:
  toString x
)
=> [ "1" "2" ]

Located at lib/lists.nix:94 in <nixpkgs>.

lib.lists.foldr

“right fold” a binary function op between successive elements of list with nul as the starting value, i.e., foldr op nul [x_1 x_2 ... x_n] == op x_1 (op x_2 ... (op x_n nul)).

Inputs
op

1. Function argument

nul

2. Function argument

list

3. Function argument

Type
foldr :: (a -> b -> b) -> b -> [a] -> b
Examples
Example 158. lib.lists.foldr usage example
concat = foldr (a: b: a + b) "z"
concat [ "a" "b" "c" ]
=> "abcz"
# different types
strange = foldr (int: str: toString (int + 1) + str) "a"
strange [ 1 2 3 4 ]
=> "2345a"

Located at lib/lists.nix:137 in <nixpkgs>.

lib.lists.fold

fold is an alias of foldr for historic reasons.

Warning

This function will be removed in 26.05.

Located at lib/lists.nix:152 in <nixpkgs>.

lib.lists.foldl

“left fold”, like foldr, but from the left:

foldl op nul [x_1 x_2 ... x_n] == op (... (op (op nul x_1) x_2) ... x_n).

Inputs
op

1. Function argument

nul

2. Function argument

list

3. Function argument

Type
foldl :: (b -> a -> b) -> b -> [a] -> b
Examples
Example 159. lib.lists.foldl usage example
lconcat = foldl (a: b: a + b) "z"
lconcat [ "a" "b" "c" ]
=> "zabc"
# different types
lstrange = foldl (str: int: str + toString (int + 1)) "a"
lstrange [ 1 2 3 4 ]
=> "a2345"

Located at lib/lists.nix:195 in <nixpkgs>.

lib.lists.foldl'

Reduce a list by applying a binary operator from left to right, starting with an initial accumulator.

Before each application of the operator, the accumulator value is evaluated. This behavior makes this function stricter than foldl.

Unlike builtins.foldl', the initial accumulator argument is evaluated before the first iteration.

A call like

foldl' op acc₀ [ x₀ x₁ x₂ ... xₙ₋₁ xₙ ]

is (denotationally) equivalent to the following, but with the added benefit that foldl' itself will never overflow the stack.

let
  acc₁   = builtins.seq acc₀   (op acc₀   x₀  );
  acc₂   = builtins.seq acc₁   (op acc₁   x₁  );
  acc₃   = builtins.seq acc₂   (op acc₂   x₂  );
  ...
  accₙ   = builtins.seq accₙ₋₁ (op accₙ₋₁ xₙ₋₁);
  accₙ₊₁ = builtins.seq accₙ   (op accₙ   xₙ  );
in
accₙ₊₁

# Or ignoring builtins.seq
op (op (... (op (op (op acc₀ x₀) x₁) x₂) ...) xₙ₋₁) xₙ
Inputs
op

The binary operation to run, where the two arguments are:

  1. acc: The current accumulator value: Either the initial one for the first iteration, or the result of the previous iteration

  2. x: The corresponding list element for this iteration

acc

The initial accumulator value.

The accumulator value is evaluated in any case before the first iteration starts.

To avoid evaluation even before the list argument is given an eta expansion can be used:

list: lib.foldl' op acc list
list

The list to fold

Type
foldl' :: (a -> b -> a) -> a -> [b] -> a
Examples
Example 160. lib.lists.foldl' usage example
foldl' (acc: x: acc + x) 0 [1 2 3]
=> 6

Located at lib/lists.nix:278 in <nixpkgs>.

lib.lists.imap0

Map with index starting from 0

Inputs
f

1. Function argument

list

2. Function argument

Type
imap0 :: (Int -> a -> b) -> [a] -> [b]
Examples
Example 161. lib.lists.imap0 usage example
imap0 (i: v: "${v}-${toString i}") ["a" "b"]
=> [ "a-0" "b-1" ]

Located at lib/lists.nix:315 in <nixpkgs>.

lib.lists.imap1

Map with index starting from 1

Inputs
f

1. Function argument

list

2. Function argument

Type
imap1 :: (Int -> a -> b) -> [a] -> [b]
Examples
Example 162. lib.lists.imap1 usage example
imap1 (i: v: "${v}-${toString i}") ["a" "b"]
=> [ "a-1" "b-2" ]

Located at lib/lists.nix:347 in <nixpkgs>.

lib.lists.ifilter0

Filter a list for elements that satisfy a predicate function. The predicate function is called with both the index and value for each element. It must return true/false to include/exclude a given element in the result. This function is strict in the result of the predicate function for each element. This function has O(n) complexity.

Also see builtins.filter (available as lib.lists.filter), which can be used instead when the index isn’t needed.

Inputs
ipred

The predicate function, it takes two arguments:

    1. (int): the index of the element.

    1. (a): the value of the element.

It must return true/false to include/exclude a given element from the result.

list

The list to filter using the predicate.

Type
ifilter0 :: (Int -> a -> Bool) -> [a] -> [a]
Examples
Example 163. lib.lists.ifilter0 usage example
ifilter0 (i: v: i == 0 || v > 2) [ 1 2 3 ]
=> [ 1 3 ]

Located at lib/lists.nix:388 in <nixpkgs>.

lib.lists.concatMap

Map and concatenate the result.

Type
concatMap :: (a -> [b]) -> [a] -> [b]
Examples
Example 164. lib.lists.concatMap usage example
concatMap (x: [x] ++ ["z"]) ["a" "b"]
=> [ "a" "z" "b" "z" ]

Located at lib/lists.nix:414 in <nixpkgs>.

lib.lists.flatten

Flatten the argument into a single list; that is, nested lists are spliced into the top-level lists.

Inputs
x

1. Function argument

Type
flatten :: [a | [a | [a | ...]]] -> [a]
Examples
Example 165. lib.lists.flatten usage example
flatten [1 [2 [3] 4] 5]
=> [1 2 3 4 5]
flatten 1
=> [1]

Located at lib/lists.nix:445 in <nixpkgs>.

lib.lists.remove

Remove elements equal to e from a list. Useful for buildInputs.

Inputs
e

Element to remove from list

list

The list

Type
remove :: a -> [a] -> [a]
Examples
Example 166. lib.lists.remove usage example
remove 3 [ 1 3 4 3 ]
=> [ 1 4 ]

Located at lib/lists.nix:477 in <nixpkgs>.

lib.lists.findSingle

Find the sole element in the list matching the specified predicate.

Returns default if no such element exists, or multiple if there are multiple matching elements.

Inputs
pred

Predicate

default

Default value to return if element was not found.

multiple

Default value to return if more than one element was found

list

Input list

Type
findSingle :: (a -> Bool) -> a -> a -> [a] -> a
Examples
Example 167. lib.lists.findSingle usage example
findSingle (x: x == 3) "none" "multiple" [ 1 3 3 ]
=> "multiple"
findSingle (x: x == 3) "none" "multiple" [ 1 3 ]
=> 3
findSingle (x: x == 3) "none" "multiple" [ 1 9 ]
=> "none"

Located at lib/lists.nix:525 in <nixpkgs>.

lib.lists.findFirstIndex

Find the first index in the list matching the specified predicate or return default if no such element exists.

Inputs
pred

Predicate

default

Default value to return

list

Input list

Type
findFirstIndex :: (a -> Bool) -> b -> [a] -> (Int | b)
Examples
Example 168. lib.lists.findFirstIndex usage example
findFirstIndex (x: x > 3) null [ 0 6 4 ]
=> 1
findFirstIndex (x: x > 9) null [ 0 6 4 ]
=> null

Located at lib/lists.nix:575 in <nixpkgs>.

lib.lists.findFirst

Find the first element in the list matching the specified predicate or return default if no such element exists.

Inputs
pred

Predicate

default

Default value to return

list

Input list

Type
findFirst :: (a -> Bool) -> a -> [a] -> a
Examples
Example 169. lib.lists.findFirst usage example
findFirst (x: x > 3) 7 [ 1 6 4 ]
=> 6
findFirst (x: x > 9) 7 [ 1 6 4 ]
=> 7

Located at lib/lists.nix:645 in <nixpkgs>.

lib.lists.any

Returns true if function pred returns true for at least one element of list.

Inputs
pred

Predicate

list

Input list

Type
any :: (a -> Bool) -> [a] -> Bool
Examples
Example 170. lib.lists.any usage example
any isString [ 1 "a" { } ]
=> true
any isString [ 1 { } ]
=> false

Located at lib/lists.nix:685 in <nixpkgs>.

lib.lists.all

Returns true if function pred returns true for all elements of list.

Inputs
pred

Predicate

list

Input list

Type
all :: (a -> Bool) -> [a] -> Bool
Examples
Example 171. lib.lists.all usage example
all (x: x < 3) [ 1 2 ]
=> true
all (x: x < 3) [ 1 2 3 ]
=> false

Located at lib/lists.nix:720 in <nixpkgs>.

lib.lists.count

Count how many elements of list match the supplied predicate function.

Inputs
pred

Predicate

Type
count :: (a -> Bool) -> [a] -> Int
Examples
Example 172. lib.lists.count usage example
count (x: x == 3) [ 3 2 3 4 6 ]
=> 2

Located at lib/lists.nix:749 in <nixpkgs>.

lib.lists.optional

Return a singleton list or an empty list, depending on a boolean value. Useful when building lists with optional elements (e.g. ++ optional (system == "i686-linux") firefox).

Inputs
cond

1. Function argument

elem

2. Function argument

Type
optional :: Bool -> a -> [a]
Examples
Example 173. lib.lists.optional usage example
optional true "foo"
=> [ "foo" ]
optional false "foo"
=> [ ]

Located at lib/lists.nix:785 in <nixpkgs>.

lib.lists.optionals

Returns a list or an empty list, depending on a boolean value.

Inputs
cond

Condition

elems

List to return if condition is true

Type
optionals :: Bool -> [a] -> [a]
Examples
Example 174. lib.lists.optionals usage example
optionals true [ 2 3 ]
=> [ 2 3 ]
optionals false [ 2 3 ]
=> [ ]

Located at lib/lists.nix:819 in <nixpkgs>.

lib.lists.toList

If argument is a list, return it; else, wrap it in a singleton list. If you’re using this, you should almost certainly reconsider if there isn’t a more “well-typed” approach.

Inputs
x

1. Function argument

Type
toList :: (a | [a]) -> [a]
Examples
Example 175. lib.lists.toList usage example
toList [ 1 2 ]
=> [ 1 2 ]
toList "hi"
=> [ "hi" ]

Located at lib/lists.nix:851 in <nixpkgs>.

lib.lists.range

Returns a list of integers from first up to and including last.

Inputs
first

First integer in the range

last

Last integer in the range

Type
range :: Int -> Int -> [Int]
Examples
Example 176. lib.lists.range usage example
range 2 4
=> [ 2 3 4 ]
range 3 2
=> [ ]

Located at lib/lists.nix:885 in <nixpkgs>.

lib.lists.replicate

Returns a list with n copies of an element.

Inputs
n

1. Function argument

elem

2. Function argument

Type
replicate :: Int -> a -> [a]
Examples
Example 177. lib.lists.replicate usage example
replicate 3 "a"
=> [ "a" "a" "a" ]
replicate 2 true
=> [ true true ]

Located at lib/lists.nix:919 in <nixpkgs>.

lib.lists.partition

Splits the elements of a list in two lists, right and wrong, depending on the evaluation of a predicate.

Inputs
pred

Predicate

list

Input list

Type
partition :: (a -> Bool) -> [a] -> { right :: [a]; wrong :: [a]; }
Examples
Example 178. lib.lists.partition usage example
partition (x: x > 2) [ 5 1 2 3 4 ]
=> { right = [ 5 3 4 ]; wrong = [ 1 2 ]; }

Located at lib/lists.nix:952 in <nixpkgs>.

lib.lists.groupBy'

Splits the elements of a list into many lists, using the return value of a predicate. Predicate should return a string which becomes keys of attrset groupBy returns. groupBy' allows to customise the combining function and initial value

Inputs
op

1. Function argument

nul

2. Function argument

pred

3. Function argument

lst

4. Function argument

Type
groupBy' :: (a -> b -> a) -> a -> (b -> String) -> [b] -> { [String] :: a }
Examples
Example 179. lib.lists.groupBy' usage example
groupBy (x: boolToString (x > 2)) [ 5 1 2 3 4 ]
=> { true = [ 5 3 4 ]; false = [ 1 2 ]; }
groupBy (x: x.name) [ {name = "icewm"; script = "icewm &";}
                      {name = "xfce";  script = "xfce4-session &";}
                      {name = "icewm"; script = "icewmbg &";}
                      {name = "mate";  script = "gnome-session &";}
                    ]
=> { icewm = [ { name = "icewm"; script = "icewm &"; }
               { name = "icewm"; script = "icewmbg &"; } ];
     mate  = [ { name = "mate";  script = "gnome-session &"; } ];
     xfce  = [ { name = "xfce";  script = "xfce4-session &"; } ];
   }

groupBy' builtins.add 0 (x: boolToString (x > 2)) [ 5 1 2 3 4 ]
=> { true = 12; false = 3; }

Located at lib/lists.nix:1007 in <nixpkgs>.

lib.lists.zipListsWith

Merges two lists of the same size together. If the sizes aren’t the same the merging stops at the shortest. How both lists are merged is defined by the first argument.

Inputs
f

Function to zip elements of both lists

fst

First list

snd

Second list

Type
zipListsWith :: (a -> b -> c) -> [a] -> [b] -> [c]
Examples
Example 180. lib.lists.zipListsWith usage example
zipListsWith (a: b: a + b) ["h" "l"] ["e" "o"]
=> ["he" "lo"]

Located at lib/lists.nix:1059 in <nixpkgs>.

lib.lists.zipLists

Merges two lists of the same size together. If the sizes aren’t the same the merging stops at the shortest.

Inputs
fst

First list

snd

Second list

Type
zipLists :: [a] -> [b] -> [{ fst :: a; snd :: b; }]
Examples
Example 181. lib.lists.zipLists usage example
zipLists [ 1 2 ] [ "a" "b" ]
=> [ { fst = 1; snd = "a"; } { fst = 2; snd = "b"; } ]

Located at lib/lists.nix:1094 in <nixpkgs>.

lib.lists.reverseList

Reverse the order of the elements of a list.

Inputs
xs

1. Function argument

Type
reverseList :: [a] -> [a]
Examples
Example 182. lib.lists.reverseList usage example
reverseList [ "b" "o" "j" ]
=> [ "j" "o" "b" ]

Located at lib/lists.nix:1122 in <nixpkgs>.

lib.lists.listDfs

Depth-First Search (DFS) for lists list != [].

before a b == true means that b depends on a (there’s an edge from b to a).

Inputs
stopOnCycles

1. Function argument

before

2. Function argument

list

3. Function argument

Type
listDfs :: Bool -> (a -> a -> Bool) -> [a] -> ({ minimal :: a; visited :: [a]; rest :: [a]; } | { cycle :: a; loops :: [a]; visited :: [a]; rest :: [a]; })
Examples
Example 183. lib.lists.listDfs usage example
listDfs true hasPrefix [ "/home/user" "other" "/" "/home" ]
  == { minimal = "/";                  # minimal element
       visited = [ "/home/user" ];     # seen elements (in reverse order)
       rest    = [ "/home" "other" ];  # everything else
     }

listDfs true hasPrefix [ "/home/user" "other" "/" "/home" "/" ]
  == { cycle   = "/";                  # cycle encountered at this element
       loops   = [ "/" ];              # and continues to these elements
       visited = [ "/" "/home/user" ]; # elements leading to the cycle (in reverse order)
       rest    = [ "/home" "other" ];  # everything else

Located at lib/lists.nix:1175 in <nixpkgs>.

lib.lists.toposort

Sort a list based on a partial ordering using DFS. This implementation is O(N^2), if your ordering is linear, use sort instead.

before a b == true means that b should be after a in the result.

Inputs
before

1. Function argument

list

2. Function argument

Type
toposort :: (a -> a -> Bool) -> [a] -> ({ result :: [a]; } | { cycle :: [a]; loops :: [a]; })
Examples
Example 184. lib.lists.toposort usage example
toposort hasPrefix [ "/home/user" "other" "/" "/home" ]
  == { result = [ "/" "/home" "/home/user" "other" ]; }

toposort hasPrefix [ "/home/user" "other" "/" "/home" "/" ]
  == { cycle = [ "/home/user" "/" "/" ]; # path leading to a cycle
       loops = [ "/" ]; }                # loops back to these elements

toposort hasPrefix [ "other" "/home/user" "/home" "/" ]
  == { result = [ "other" "/" "/home" "/home/user" ]; }

toposort (a: b: a < b) [ 3 2 1 ] == { result = [ 1 2 3 ]; }

Located at lib/lists.nix:1246 in <nixpkgs>.

lib.lists.sort

Sort a list based on a comparator function which compares two elements and returns true if the first argument is strictly below the second argument. The returned list is sorted in an increasing order. The implementation does a quick-sort.

See also sortOn, which applies the default comparison on a function-derived property, and may be more efficient.

Inputs
comparator

1. Function argument

list

2. Function argument

Type
sort :: (a -> a -> Bool) -> [a] -> [a]
Examples
Example 185. lib.lists.sort usage example
sort (p: q: p < q) [ 5 3 7 ]
=> [ 3 5 7 ]

Located at lib/lists.nix:1305 in <nixpkgs>.

lib.lists.sortOn

Sort a list based on the default comparison of a derived property b.

The items are returned in b-increasing order.

Performance:

The passed function f is only evaluated once per item, unlike an unprepared sort using f p < f q.

Laws:

sortOn f == sort (p: q: f p < f q)
Inputs
f

1. Function argument

list

2. Function argument

Type
sortOn :: (a -> b) -> [a] -> [a], for comparable b
Examples
Example 186. lib.lists.sortOn usage example
sortOn stringLength [ "aa" "b" "cccc" ]
=> [ "b" "aa" "cccc" ]

Located at lib/lists.nix:1350 in <nixpkgs>.

lib.lists.compareLists

Compare two lists element-by-element with a comparison function cmp.

List elements are compared pairwise in order by the provided comparison function cmp, the first non-equal pair of elements determines the result.

Note

The < operator can also be used to compare lists using a boolean condition. (e.g. [1 2] < [1 3] is true). See also language operators for more information.

Inputs
cmp

The comparison function a: b: ... must return:

  • 0 if a and b are equal

  • 1 if a is greater than b

  • -1 if a is less than b

See lib.compare for a an example implementation.

a

The first list

b

The second list

Type
compareLists :: (a -> a -> Int) -> [a] -> [a] -> Int
Examples
Example 187. lib.lists.compareLists usage examples
compareLists lib.compare [] []
=> 0
compareLists lib.compare [] [ "a" ]
=> -1
compareLists lib.compare [ "a" ] []
=> 1
compareLists lib.compare [ "a" "b" ] [ "a" "c" ]
=> -1

Located at lib/lists.nix:1420 in <nixpkgs>.

lib.lists.naturalSort

Sort list using “Natural sorting”. Numeric portions of strings are sorted in numeric order.

Inputs
lst

1. Function argument

Type
naturalSort :: [String] -> [String]
Examples
Example 188. lib.lists.naturalSort usage example
naturalSort ["disk11" "disk8" "disk100" "disk9"]
=> ["disk8" "disk9" "disk11" "disk100"]
naturalSort ["10.46.133.149" "10.5.16.62" "10.54.16.25"]
=> ["10.5.16.62" "10.46.133.149" "10.54.16.25"]
naturalSort ["v0.2" "v0.15" "v0.0.9"]
=> [ "v0.0.9" "v0.2" "v0.15" ]

Located at lib/lists.nix:1463 in <nixpkgs>.

lib.lists.take

Returns the first (at most) N elements of a list.

Inputs
count

Number of elements to take

list

Input list

Type
take :: Int -> [a] -> [a]
Examples
Example 189. lib.lists.take usage example
take 2 [ "a" "b" "c" "d" ]
=> [ "a" "b" ]
take 2 [ ]
=> [ ]

Located at lib/lists.nix:1507 in <nixpkgs>.

lib.lists.takeEnd

Returns the last (at most) N elements of a list.

Inputs
count

Maximum number of elements to pick

list

Input list

Type
takeEnd :: Int -> [a] -> [a]
Examples
Example 190. lib.lists.takeEnd usage example
takeEnd 2 [ "a" "b" "c" "d" ]
=> [ "c" "d" ]
takeEnd 2 [ ]
=> [ ]

Located at lib/lists.nix:1541 in <nixpkgs>.

lib.lists.drop

Remove the first (at most) N elements of a list.

Inputs
count

Number of elements to drop

list

Input list

Type
drop :: Int -> [a] -> [a]
Examples
Example 191. lib.lists.drop usage example
drop 2 [ "a" "b" "c" "d" ]
=> [ "c" "d" ]
drop 2 [ ]
=> [ ]

Located at lib/lists.nix:1575 in <nixpkgs>.

lib.lists.dropEnd

Remove the last (at most) N elements of a list.

Inputs
count

Number of elements to drop

list

Input list

Type
dropEnd :: Int -> [a] -> [a]
Examples
Example 192. lib.lists.dropEnd usage example
  dropEnd 2 [ "a" "b" "c" "d" ]
  => [ "a" "b" ]
  dropEnd 2 [ ]
  => [ ]

Located at lib/lists.nix:1609 in <nixpkgs>.

lib.lists.hasPrefix

Whether the first list is a prefix of the second list.

Inputs
list1

1. Function argument

list2

2. Function argument

Type
hasPrefix :: [a] -> [a] -> Bool
Examples
Example 193. lib.lists.hasPrefix usage example
hasPrefix [ 1 2 ] [ 1 2 3 4 ]
=> true
hasPrefix [ 0 1 ] [ 1 2 3 4 ]
=> false

Located at lib/lists.nix:1643 in <nixpkgs>.

lib.lists.removePrefix

Remove the first list as a prefix from the second list. Error if the first list isn’t a prefix of the second list.

Inputs
list1

1. Function argument

list2

2. Function argument

Type
removePrefix :: [a] -> [a] -> [a]
Examples
Example 194. lib.lists.removePrefix usage example
removePrefix [ 1 2 ] [ 1 2 3 4 ]
=> [ 3 4 ]
removePrefix [ 0 1 ] [ 1 2 3 4 ]
=> <error>

Located at lib/lists.nix:1678 in <nixpkgs>.

lib.lists.sublist

Returns a list consisting of at most count elements of list, starting at index start.

Inputs
start

Index at which to start the sublist

count

Number of elements to take

list

Input list

Type
sublist :: Int -> Int -> [a] -> [a]
Examples
Example 195. lib.lists.sublist usage example
sublist 1 3 [ "a" "b" "c" "d" "e" ]
=> [ "b" "c" "d" ]
sublist 1 3 [ ]
=> [ ]

Located at lib/lists.nix:1722 in <nixpkgs>.

lib.lists.commonPrefix

The common prefix of two lists.

Inputs
list1

1. Function argument

list2

2. Function argument

Type
commonPrefix :: [a] -> [a] -> [a]
Examples
Example 196. lib.lists.commonPrefix usage example
commonPrefix [ 1 2 3 4 5 6 ] [ 1 2 4 8 ]
=> [ 1 2 ]
commonPrefix [ 1 2 3 ] [ 1 2 3 4 5 ]
=> [ 1 2 3 ]
commonPrefix [ 1 2 3 ] [ 4 5 6 ]
=> [ ]

Located at lib/lists.nix:1770 in <nixpkgs>.

lib.lists.last

Returns the last element of a list.

This function throws an error if the list is empty.

Inputs
list

1. Function argument

Type
last :: [a] -> a
Examples
Example 197. lib.lists.last usage example
last [ 1 2 3 ]
=> 3

Located at lib/lists.nix:1811 in <nixpkgs>.

lib.lists.init

Returns all elements but the last.

This function throws an error if the list is empty.

Inputs
list

1. Function argument

Type
init :: [a] -> [a]
Examples
Example 198. lib.lists.init usage example
init [ 1 2 3 ]
=> [ 1 2 ]

Located at lib/lists.nix:1844 in <nixpkgs>.

lib.lists.crossLists

Returns the image of the cross product of some lists by a function.

Examples
Example 199. lib.lists.crossLists usage example
crossLists (x: y: "${toString x}${toString y}") [[1 2] [3 4]]
=> [ "13" "14" "23" "24" ]

If you have an attrset already, consider mapCartesianProduct:

mapCartesianProduct (x: "${toString x.a}${toString x.b}") { a = [1 2]; b = [3 4]; }
=> [ "13" "14" "23" "24" ]

Located at lib/lists.nix:1869 in <nixpkgs>.

lib.lists.unique

Remove duplicate elements from the list. O(n^2) complexity.

Note

If the list only contains strings and order is not important, the complexity can be reduced to O(n log n) by using lib.lists.uniqueStrings instead.

Inputs
list

Input list

Type
unique :: [a] -> [a]
Examples
Example 200. lib.lists.unique usage example
unique [ 3 2 3 4 ]
=> [ 3 2 4 ]

Located at lib/lists.nix:1901 in <nixpkgs>.

lib.lists.uniqueStrings

Removes duplicate strings from the list. O(n log n) complexity.

Note

Order is not preserved.

All elements of the list must be strings without context.

This function fails when the list contains a non-string element or a string with context. In that case use lib.lists.unique instead.

Inputs
list

List of strings

Type
uniqueStrings :: [String] -> [String]
Examples
Example 201. lib.lists.uniqueStrings usage example
uniqueStrings [ "foo" "bar" "foo" ]
=> [ "bar" "foo" ] # order is not preserved

Located at lib/lists.nix:1938 in <nixpkgs>.

lib.lists.allUnique

Check if list contains only unique elements. O(n^2) complexity.

Inputs
list

1. Function argument

Type
allUnique :: [a] -> Bool
Examples
Example 202. lib.lists.allUnique usage example
allUnique [ 3 2 3 4 ]
=> false
allUnique [ 3 2 4 1 ]
=> true

Located at lib/lists.nix:1968 in <nixpkgs>.

lib.lists.intersectLists

Intersects list list1 and another list (list2).

O(nm) complexity.

Inputs
list1

First list

list2

Second list

Type
intersectLists :: [a] -> [a] -> [a]
Examples
Example 203. lib.lists.intersectLists usage example
intersectLists [ 1 2 3 ] [ 6 3 2 ]
=> [ 3 2 ]

Located at lib/lists.nix:2002 in <nixpkgs>.

lib.lists.subtractLists

Subtracts list e from another list (list2).

O(nm) complexity.

Inputs
e

First list

list2

Second list

Type
subtractLists :: [a] -> [a] -> [a]
Examples
Example 204. lib.lists.subtractLists usage example
subtractLists [ 3 2 ] [ 1 2 3 4 5 3 ]
=> [ 1 4 5 ]

Located at lib/lists.nix:2036 in <nixpkgs>.

lib.lists.mutuallyExclusive

Test if two lists have no common element. It should be slightly more efficient than intersectLists a b == [].

Inputs
a

1. Function argument

b

2. Function argument

Type
mutuallyExclusive :: [a] -> [a] -> Bool

Located at lib/lists.nix:2058 in <nixpkgs>.

lib.lists.concatAttrValues

Concatenate all attributes of an attribute set. This assumes that every attribute of the set is a list.

Inputs
set

Attribute set with attributes that are lists

Type
concatAttrValues :: { [String] :: [a] } -> [a]
Examples
Example 205. lib.concatAttrValues usage example
concatAttrValues { a = [ 1 2 ]; b = [ 3 ]; }
=> [ 1 2 3 ]

Located at lib/lists.nix:2087 in <nixpkgs>.

lib.lists.replaceElemAt

Replaces a list’s nth element with a new element

Inputs
list

Input list

idx

index to replace

newElem

new element to replace with

Type
replaceElemAt :: [a] -> Int -> a -> [a]
Examples
Example 206. replaceElemAt usage example
lib.replaceElemAt` [1 2 3] 0 "a"
=> ["a" 2 3]

Located at lib/lists.nix:2120 in <nixpkgs>.

lib.debug: debugging functions

Collection of functions useful for debugging broken nix expressions.

  • trace-like functions take two values, print the first to stderr and return the second.

  • traceVal-like functions take one argument which both printed and returned.

  • traceSeq-like functions fully evaluate their traced value before printing (not just to “weak head normal form” like trace does by default).

  • Functions that end in -Fn take an additional function as their first argument, which is applied to the traced value before it is printed.

lib.debug.traceIf

Conditionally trace the supplied message, based on a predicate.

Inputs
pred

Predicate to check

msg

Message that should be traced

x

Value to return

Type
traceIf :: Bool -> String -> a -> a
Examples
Example 207. lib.debug.traceIf usage example
traceIf true "hello" 3
trace: hello
=> 3

Located at lib/debug.nix:78 in <nixpkgs>.

lib.debug.traceValFn

Trace the supplied value after applying a function to it, and return the original value.

Inputs
f

Function to apply

x

Value to trace and return

Type
traceValFn :: (a -> b) -> a -> a
Examples
Example 208. lib.debug.traceValFn usage example
traceValFn (v: "mystring ${v}") "foo"
trace: mystring foo
=> "foo"

Located at lib/debug.nix:114 in <nixpkgs>.

lib.debug.traceVal

Trace the supplied value and return it.

Inputs
x

Value to trace and return

Type
traceVal :: a -> a
Examples
Example 209. lib.debug.traceVal usage example
traceVal 42
# trace: 42
=> 42

Located at lib/debug.nix:143 in <nixpkgs>.

lib.debug.traceSeq

builtins.trace, but the value is builtins.deepSeqed first.

Inputs
x

The value to trace

y

The value to return

Type
traceSeq :: a -> b -> b
Examples
Example 210. lib.debug.traceSeq usage example
trace { a.b.c = 3; } null
trace: { a = <thunk>; }
=> null
traceSeq { a.b.c = 3; } null
trace: { a = { b = { c = 3; }; }; }
=> null

Located at lib/debug.nix:179 in <nixpkgs>.

lib.debug.traceSeqN

Like traceSeq, but only evaluate down to depth n. This is very useful because lots of traceSeq usages lead to an infinite recursion.

Inputs
depth

1. Function argument

x

2. Function argument

y

3. Function argument

Type
traceSeqN :: Int -> a -> b -> b
Examples
Example 211. lib.debug.traceSeqN usage example
traceSeqN 2 { a.b.c = 3; } null
trace: { a = { b = {…}; }; }
=> null

Located at lib/debug.nix:218 in <nixpkgs>.

lib.debug.traceValSeqFn

A combination of traceVal and traceSeq that applies a provided function to the value to be traced after deepSeqing it.

Inputs
f

Function to apply

v

Value to trace

Type
traceValSeqFn :: (a -> b) -> a -> a
Examples
Example 212. lib.debug.traceValSeqFn usage example
traceValSeqFn (v: v // { d = "foo";}) { a.b.c = 3; }
trace: { a = { b = { c = 3; }; }; d = "foo"; }
=> { a = { ... }; }


Located at lib/debug.nix:278 in <nixpkgs>.

lib.debug.traceValSeq

A combination of traceVal and traceSeq.

Inputs
v

Value to trace

Type
traceValSeq :: a -> a
Examples
Example 213. lib.debug.traceValSeq usage example
traceValSeq { a.b.c = 3; }
trace: { a = { b = { c = 3; }; }; }
=> { a = { ... }; }

Located at lib/debug.nix:307 in <nixpkgs>.

lib.debug.traceValSeqNFn

A combination of traceVal and traceSeqN that applies a provided function to the value to be traced.

Inputs
f

Function to apply

depth

2. Function argument

v

Value to trace

Type
traceValSeqNFn :: (a -> b) -> Int -> a -> a
Examples
Example 214. lib.debug.traceValSeqNFn usage example
traceValSeqNFn (v: v // { d = "foo";}) 2 { a.b.c = 3; }
trace: { a = { b = {…}; }; d = "foo"; }
=> { a = { ... }; }

Located at lib/debug.nix:345 in <nixpkgs>.

lib.debug.traceValSeqN

A combination of traceVal and traceSeqN.

Inputs
depth

1. Function argument

v

Value to trace

Type
traceValSeqN :: Int -> a -> a
Examples
Example 215. lib.debug.traceValSeqN usage example
traceValSeqN 2 { a.b.c = 3; }
trace: { a = { b = {…}; }; }
=> { a = { ... }; }

Located at lib/debug.nix:380 in <nixpkgs>.

lib.debug.traceFnSeqN

Trace the input and output of a function f named name, both down to depth.

This is useful for adding around a function call, to see the before/after of values as they are transformed.

Inputs
depth

1. Function argument

name

2. Function argument

f

3. Function argument

v

4. Function argument

Type
traceFnSeqN :: Int -> String -> (a -> b) -> a -> b
Examples
Example 216. lib.debug.traceFnSeqN usage example
traceFnSeqN 2 "id" (x: x) { a.b.c = 3; }
trace: { fn = "id"; from = { a.b = {…}; }; to = { a.b = {…}; }; }
=> { a = { ... }; }

Located at lib/debug.nix:425 in <nixpkgs>.

lib.debug.runTests

Evaluates a set of tests.

A test is an attribute set {expr, expected}, denoting an expression and its expected result.

The result is a list of failed tests, each represented as {name, expected, result},

  • expected

    • What was passed as expected

  • result

    • The actual result of the test

Used for regression testing of the functions in lib; see tests.nix for more examples.

Important: Only attributes that start with test are executed.

  • If you want to run only a subset of the tests add the attribute tests = ["testName"];

Inputs
tests

Tests to run

Type
runTests :: {
  tests :: [String];
  ${testName} :: {
    expr :: a;
    expected :: a;
  };
}
->
[
  {
    name :: String;
    expected :: a;
    result :: a;
  }
]
Examples
Example 217. lib.debug.runTests usage example
runTests {
  testAndOk = {
    expr = lib.and true false;
    expected = false;
  };
  testAndFail = {
    expr = lib.and true false;
    expected = true;
  };
}
->
[
  {
    name = "testAndFail";
    expected = true;
    result = false;
  }
]

Located at lib/debug.nix:512 in <nixpkgs>.

lib.debug.throwTestFailures

Pretty-print a list of test failures.

This takes an attribute set containing failures (a list of test failures produced by runTests) and pretty-prints each failing test, before throwing an error containing the raw test data as JSON.

If the input list is empty, null is returned.

Inputs
failures

A list of test failures (produced runTests), each containing name, expected, and result attributes.

Type
throwTestFailures :: {
  failures = [
    {
      name :: String;
      expected :: a;
      result :: a;
    }
  ];
}
->
Null
Examples
Example 218. lib.debug.throwTestFailures usage example
throwTestFailures {
  failures = [
    {
      name = "testDerivation";
      expected = derivation {
        name = "a";
        builder = "bash";
        system = "x86_64-linux";
      };
      result = derivation {
        name = "b";
        builder = "bash";
        system = "x86_64-linux";
      };
    }
  ];
}
->
trace: FAIL testDerivation:
  Expected: <derivation a>
    Result: <derivation b>

error:
       … while evaluating the file '...':

       … caused by explicit throw
         at /nix/store/.../lib/debug.nix:528:7:
          527|       in
          528|       throw (
             |       ^
          529|         builtins.seq traceFailures (

       error: 1 tests failed:
       - testDerivation

       [{"expected":"/nix/store/xh7kyqp69mxkwspmi81a94m9xx74r8dr-a","name":"testDerivation","result":"/nix/store/503l84nir4zw57d1shfhai25bxxn16c6-b"}]
null

Located at lib/debug.nix:619 in <nixpkgs>.

lib.debug.testAllTrue

Create a test assuming that list elements are true.

Inputs
expr

1. Function argument

Examples
Example 219. lib.debug.testAllTrue usage example
{ testX = allTrue [ true ]; }

Located at lib/debug.nix:682 in <nixpkgs>.

lib.options: NixOS / nixpkgs option handling

Module System option handling.

lib.options.isOption

Returns true when the given argument a is an option

Inputs
a

Any value to check whether it is an option

Examples
Example 220. lib.options.isOption usage example
isOption 1             // => false
isOption (mkOption {}) // => true

Type
isOption :: Any -> Bool

Located at lib/options.nix:77 in <nixpkgs>.

lib.options.mkOption

Creates an Option declaration for use with the module system.

Inputs
Attribute set

containing none or some of the following attributes.

default

Optional default value used when no definition is given in the configuration.

defaultText

Substitute for documenting the default, if evaluating the default value during documentation rendering is not possible.

Can be any nix value that evaluates.

Usage with lib.literalMD or lib.literalExpression is supported

example

Optional example value used in the manual.

Can be any nix value that evaluates.

Usage with lib.literalMD or lib.literalExpression is supported

description

Optional string describing the option. This is required if option documentation is generated.

relatedPackages

Optional related packages used in the manual (see genRelatedPackages in ../nixos/lib/make-options-doc/default.nix).

type

Optional option type, providing type-checking and value merging.

apply

Optional function that converts the option value to something else.

internal

Optional boolean indicating whether the option is for NixOS developers only.

visible

Optional, whether the option and/or sub-options show up in the manual. Use false to hide the option and any sub-options from submodules. Use “shallow” to hide only sub-options. Use “transparent” to hide this option, but not its sub-options. Default: true.

readOnly

Optional boolean indicating whether the option can be set only once.

Examples
Example 221. lib.options.mkOption usage example
mkOption { }
# => Empty option; type = types.anything

mkOption { default = "foo"; }
# => Same as above, with a default value

Located at lib/options.nix:139 in <nixpkgs>.

lib.options.mkEnableOption

Creates an option declaration with a default value of false, and can be defined to true.

Inputs
name

Name for the created option

Examples
Example 222. lib.options.mkEnableOption usage example
# module
let
  eval = lib.evalModules {
    modules = [
      {
        options.foo.enable = mkEnableOption "foo";

        config.foo.enable = true;
      }
    ];
  };
in
eval.config
=> { foo.enable = true; }

Located at lib/options.nix:186 in <nixpkgs>.

lib.options.mkPackageOption

Creates an Option attribute set for an option that specifies the package a module should use for some purpose.

The package is specified in the third argument under default as a list of strings representing its attribute path in nixpkgs (or another package set). Because of this, you need to pass nixpkgs itself (usually pkgs in a module; alternatively to nixpkgs itself, another package set) as the first argument.

If you pass another package set you should set the pkgsText option. This option is used to display the expression for the package set. It is "pkgs" by default. If your expression is complex you should parenthesize it, as the pkgsText argument is usually immediately followed by an attribute lookup (.).

The second argument may be either a string or a list of strings. It provides the display name of the package in the description of the generated option (using only the last element if the passed value is a list) and serves as the fallback value for the default argument.

To include extra information in the description, pass extraDescription to append arbitrary text to the generated description.

You can also pass an example value, either a literal string or an attribute path.

The default argument can be omitted if the provided name is an attribute of pkgs (if name is a string) or a valid attribute path in pkgs (if name is a list). You can also set default to just a string in which case it is interpreted as an attribute name (a singleton attribute path, if you will).

If you wish to explicitly provide no default, pass null as default.

If you want users to be able to set no package, pass nullable = true. In this mode a default = null will not be interpreted as no default and is interpreted literally.

Inputs
pkgs

Package set (an instantiation of nixpkgs such as pkgs in modules or another package set)

name

Name for the package, shown in option description

Structured function argument

Attribute set containing the following attributes.

nullable

Optional whether the package can be null, for example to disable installing a package altogether. Default: false

default

Optional attribute path where the default package is located. Default: name If omitted will be copied from name

example

Optional string or an attribute path to use as an example. Default: null

extraDescription

Optional additional text to include in the option description. Default: ""

pkgsText

Optional representation of the package set passed as pkgs. Default: "pkgs"

Type
mkPackageOption :: Pkgs -> (String | [String]) -> { nullable? :: Bool; default? :: String | [String]; example? :: Null | String | [String]; extraDescription? :: String; pkgsText? :: String; } -> Option
Examples
Example 223. lib.options.mkPackageOption usage example
mkPackageOption pkgs "hello" { }
=> { ...; default = pkgs.hello; defaultText = literalExpression "pkgs.hello"; description = "The hello package to use."; type = package; }

mkPackageOption pkgs "GHC" {
  default = [ "ghc" ];
  example = "pkgs.haskellPackages.ghc.withPackages (hkgs: [ hkgs.primes ])";
}
=> { ...; default = pkgs.ghc; defaultText = literalExpression "pkgs.ghc"; description = "The GHC package to use."; example = literalExpression "pkgs.haskellPackages.ghc.withPackages (hkgs: [ hkgs.primes ])"; type = package; }

mkPackageOption pkgs [ "python3Packages" "pytorch" ] {
  extraDescription = "This is an example and doesn't actually do anything.";
}
=> { ...; default = pkgs.python3Packages.pytorch; defaultText = literalExpression "pkgs.python3Packages.pytorch"; description = "The pytorch package to use. This is an example and doesn't actually do anything."; type = package; }

mkPackageOption pkgs "nushell" {
  nullable = true;
}
=> { ...; default = pkgs.nushell; defaultText = literalExpression "pkgs.nushell"; description = "The nushell package to use."; type = nullOr package; }

mkPackageOption pkgs "coreutils" {
  default = null;
}
=> { ...; description = "The coreutils package to use."; type = package; }

mkPackageOption pkgs "dbus" {
  nullable = true;
  default = null;
}
=> { ...; default = null; description = "The dbus package to use."; type = nullOr package; }

mkPackageOption pkgs.javaPackages "OpenJFX" {
  default = "openjfx20";
  pkgsText = "pkgs.javaPackages";
}
=> { ...; default = pkgs.javaPackages.openjfx20; defaultText = literalExpression "pkgs.javaPackages.openjfx20"; description = "The OpenJFX package to use."; type = package; }

Located at lib/options.nix:308 in <nixpkgs>.

lib.options.mkSinkUndeclaredOptions

This option accepts arbitrary definitions, but it does not produce an option value.

This is useful for sharing a module across different module sets without having to implement similar features as long as the values of the options are not accessed.

Inputs
attrs

Attribute set whose attributes override the argument to mkOption.

Located at lib/options.nix:360 in <nixpkgs>.

lib.options.mergeDefaultOption

A merge function that merges multiple definitions of an option into a single value

Caution

This function is used as the default merge operation in lib.types.mkOptionType. In most cases, explicit usage of this function is unnecessary.

Inputs
loc

location of the option in the configuration as a list of strings.

e.g. ["boot" "loader "grub" "enable"]

defs

list of definition values and locations.

e.g. [ { file = "/foo.nix"; value = 1; } { file = "/bar.nix"; value = 2 } ]

Example
Example 224. lib.options.mergeDefaultOption usage example
myType = mkOptionType {
  name = "myType";
  merge = mergeDefaultOption; # <- This line is redundant. It is the default already.
};

Merge behavior

Merging requires all definition values to have the same type.

  • If all definitions are booleans, the result of a foldl' with the or operation is returned.

  • If all definitions are strings, they are concatenated. (lib.concatStrings)

  • If all definitions are integers and all are equal, the first one is returned.

  • If all definitions are lists, they are concatenated. (++)

  • If all definitions are attribute sets, they are merged. (lib.mergeAttrs)

  • If all definitions are functions, the first function is applied to the result of the second function. (f -> x: f x)

  • Otherwise, an error is thrown.

Located at lib/options.nix:422 in <nixpkgs>.

lib.options.mergeOneOption

Require a single definition.

Warning

Does not perform nested checks, as this does not run the merge function!

Located at lib/options.nix:451 in <nixpkgs>.

lib.options.mergeUniqueOption

Require a single definition.

Note

When the type is not checked completely by check, pass a merge function for further checking (of sub-attributes, etc).

Inputs
loc

2. Function argument

defs

3. Function argument

Located at lib/options.nix:470 in <nixpkgs>.

lib.options.mergeEqualOption

“Merge” option definitions by checking that they all have the same value.

Inputs
loc

1. Function argument

defs

2. Function argument

Located at lib/options.nix:499 in <nixpkgs>.

lib.options.getValues

Extracts values of all value keys of the given list.

Type
getValues :: [{ value :: a; ... }] -> [a]
Examples
Example 225. getValues usage example
getValues [ { value = 1; } { value = 2; } ] // => [ 1 2 ]
getValues [ ]                               // => [ ]

Located at lib/options.nix:542 in <nixpkgs>.

lib.options.getFiles

Extracts values of all file keys of the given list

Type
getFiles :: [{ file :: a; ... }] -> [a]
Examples
Example 226. getFiles usage example
getFiles [ { file = "file1"; } { file = "file2"; } ] // => [ "file1" "file2" ]
getFiles [ ]                                         // => [ ]

Located at lib/options.nix:564 in <nixpkgs>.

lib.options.scrubOptionValue

This function recursively removes all derivation attributes from x except for the name attribute.

This is to make the generation of options.xml much more efficient: the XML representation of derivations is very large (on the order of megabytes) and is not actually used by the manual generator.

This function was made obsolete by renderOptionValue and is kept for compatibility with out-of-tree code.

Inputs
x

1. Function argument

Located at lib/options.nix:645 in <nixpkgs>.

lib.options.renderOptionValue

Ensures that the given option value (default or example) is a _typed string by rendering Nix values to literalExpressions.

Inputs
v

1. Function argument

Located at lib/options.nix:671 in <nixpkgs>.

lib.options.literalExpression

For use in the defaultText and example option attributes. Causes the given string to be rendered verbatim in the documentation as Nix code. This is necessary for complex values, e.g. functions, or values that depend on other values or packages.

Examples
Example 227. literalExpression usage example
llvmPackages = mkOption {
  type = types.str;
  description = ''
    Version of llvm packages to use for
    this module
  '';
  example = literalExpression ''
    llvmPackages = pkgs.llvmPackages_20;
  '';
};

Inputs
text

The text to render as a Nix expression

Located at lib/options.nix:714 in <nixpkgs>.

lib.options.literalCode

For use in the defaultText and example option attributes. Causes the given string to be rendered verbatim in the documentation as a code block with the language bassed on the provided input tag.

If you wish to render Nix code, please see literalExpression.

Examples
Example 228. literalCode usage example
myPythonScript = mkOption {
  type = types.str;
  description = ''
    Example python script used by a module
  '';
  example = literalCode "python" ''
    print("Hello world!")
  '';
};

Inputs
languageTag

The language tag to use when producing the code block (i.e. js, rs, etc).

text

The text to render as a Nix expression

Located at lib/options.nix:759 in <nixpkgs>.

lib.options.literalMD

For use in the defaultText and example option attributes. Causes the given MD text to be inserted verbatim in the documentation, for when a literalExpression would be too hard to read.

Inputs
text

1. Function argument

Located at lib/options.nix:778 in <nixpkgs>.

lib.options.showOption

Convert an option, described as a list of the option parts to a human-readable version.

Inputs
parts

1. Function argument

Examples
Example 229. showOption usage example
(showOption ["foo" "bar" "baz"]) == "foo.bar.baz"
  (showOption ["foo" "bar.baz" "tux"]) == "foo.\"bar.baz\".tux"
  (showOption ["windowManager" "2bwm" "enable"]) == "windowManager.\"2bwm\".enable"

Placeholders will not be quoted as they are not actual values:
  (showOption ["foo" "*" "bar"]) == "foo.*.bar"
  (showOption ["foo" "<name>" "bar"]) == "foo.<name>.bar"
  (showOption ["foo" "<myPlaceholder>" "bar"]) == "foo.<myPlaceholder>.bar"

Located at lib/options.nix:817 in <nixpkgs>.

lib.options.showOptionWithDefLocs

Pretty prints all option definition locations

Inputs
option

The option to pretty print

Examples
Example 230. lib.options.showOptionWithDefLocs usage example
showOptionWithDefLocs { loc = ["x" "y" ]; files = [ "foo.nix" "bar.nix" ];  }
"x.y, with values defined in:\n  - foo.nix\n  - bar.nix\n"
nix-repl> eval = lib.evalModules {
    modules = [
      {
        options = {
          foo = lib.mkEnableOption "foo";
        };
      }
    ];
  }

nix-repl> lib.options.showOptionWithDefLocs eval.options.foo
"foo, with values defined in:\n  - <unknown-file>\n"

Type
showOptionWithDefLocs :: { files :: [String]; loc :: [String]; ... } -> String

Located at lib/options.nix:905 in <nixpkgs>.

lib.path: path functions

lib.path.append

Append a subpath string to a path.

Like path + ("/" + string) but safer, because it errors instead of returning potentially surprising results. More specifically, it checks that the first argument is a path value type, and that the second argument is a valid subpath string.

Laws:

  • Not influenced by subpath normalisation:

    append p s == append p (subpath.normalise s)
    
Inputs
path

The absolute path to append to

subpath

The subpath string to append

Type
append :: Path -> String -> Path
Examples
Example 231. append usage example
append /foo "bar/baz"
=> /foo/bar/baz

# subpaths don't need to be normalised
append /foo "./bar//baz/./"
=> /foo/bar/baz

# can append to root directory
append /. "foo/bar"
=> /foo/bar

# first argument needs to be a path value type
append "/foo" "bar"
=> <error>

# second argument needs to be a valid subpath string
append /foo /bar
=> <error>
append /foo ""
=> <error>
append /foo "/bar"
=> <error>
append /foo "../bar"
=> <error>

Located at lib/path/default.nix:236 in <nixpkgs>.

lib.path.hasPrefix

Whether the first path is a component-wise prefix of the second path.

Laws:

Inputs
path1

1. Function argument

Type
hasPrefix :: Path -> Path -> Bool
Examples
Example 232. hasPrefix usage example
hasPrefix /foo /foo/bar
=> true
hasPrefix /foo /foo
=> true
hasPrefix /foo/bar /foo
=> false
hasPrefix /. /foo
=> true

Located at lib/path/default.nix:286 in <nixpkgs>.

lib.path.removePrefix

Remove the first path as a component-wise prefix from the second path. The result is a normalised subpath string.

Laws:

Inputs
path1

1. Function argument

Type
removePrefix :: Path -> Path -> String
Examples
Example 233. removePrefix usage example
removePrefix /foo /foo/bar/baz
=> "./bar/baz"
removePrefix /foo /foo
=> "./."
removePrefix /foo/bar /foo
=> <error>
removePrefix /. /foo
=> "./foo"

Located at lib/path/default.nix:345 in <nixpkgs>.

lib.path.splitRoot

Split the filesystem root from a path. The result is an attribute set with these attributes:

  • root: The filesystem root of the path, meaning that this directory has no parent directory.

  • subpath: The normalised subpath string that when appended to root returns the original path.

Laws:

  • Appending the root and subpath gives the original path:

    p ==
      append
        (splitRoot p).root
        (splitRoot p).subpath
    
  • Trying to get the parent directory of root using dirOf returns root itself:

    dirOf (splitRoot p).root == (splitRoot p).root
    
Inputs
path

The path to split the root off of

Type
splitRoot :: Path -> { root :: Path; subpath :: String; }
Examples
Example 234. splitRoot usage example
splitRoot /foo/bar
=> { root = /.; subpath = "./foo/bar"; }

splitRoot /.
=> { root = /.; subpath = "./."; }

# Nix neutralises `..` path components for all path values automatically
splitRoot /foo/../bar
=> { root = /.; subpath = "./bar"; }

splitRoot "/foo/bar"
=> <error>

Located at lib/path/default.nix:422 in <nixpkgs>.

lib.path.hasStorePathPrefix

Whether a path has a store path as a prefix.

Note

As with all functions of this lib.path library, it does not work on paths in strings, which is how you’d typically get store paths.

Instead, this function only handles path values themselves, which occur when Nix files in the store use relative path expressions.

Inputs
path

1. Function argument

Type
hasStorePathPrefix :: Path -> Bool
Examples
Example 235. hasStorePathPrefix usage example
# Subpaths of derivation outputs have a store path as a prefix
hasStorePathPrefix /nix/store/nvl9ic0pj1fpyln3zaqrf4cclbqdfn1j-foo/bar/baz
=> true

# The store directory itself is not a store path
hasStorePathPrefix /nix/store
=> false

# Derivation outputs are store paths themselves
hasStorePathPrefix /nix/store/nvl9ic0pj1fpyln3zaqrf4cclbqdfn1j-foo
=> true

# Paths outside the Nix store don't have a store path prefix
hasStorePathPrefix /home/user
=> false

# Not all paths under the Nix store are store paths
hasStorePathPrefix /nix/store/.links/10gg8k3rmbw8p7gszarbk7qyd9jwxhcfq9i6s5i0qikx8alkk4hq
=> false

# Store derivations are also store paths themselves
hasStorePathPrefix /nix/store/nvl9ic0pj1fpyln3zaqrf4cclbqdfn1j-foo.drv
=> true

Located at lib/path/default.nix:492 in <nixpkgs>.

lib.path.subpath.isValid

Whether a value is a valid subpath string.

A subpath string points to a specific file or directory within an absolute base directory. It is a stricter form of a relative path that excludes .. components, since those could escape the base directory.

  • The value is a string.

  • The string is not empty.

  • The string doesn’t start with a /.

  • The string doesn’t contain any .. path components.

Inputs
value

The value to check

Type
subpath.isValid :: String -> Bool
Examples
Example 236. subpath.isValid usage example
# Not a string
subpath.isValid null
=> false

# Empty string
subpath.isValid ""
=> false

# Absolute path
subpath.isValid "/foo"
=> false

# Contains a `..` path component
subpath.isValid "../foo"
=> false

# Valid subpath
subpath.isValid "foo/bar"
=> true

# Doesn't need to be normalised
subpath.isValid "./foo//bar/"
=> true

Located at lib/path/default.nix:565 in <nixpkgs>.

lib.path.subpath.join

Join subpath strings together using /, returning a normalised subpath string.

Like concatStringsSep "/" but safer, specifically:

  • All elements must be valid subpath strings.

  • The result gets normalised.

  • The edge case of an empty list gets properly handled by returning the neutral subpath "./.".

Laws:

  • Associativity:

    subpath.join [ x (subpath.join [ y z ]) ] == subpath.join [ (subpath.join [ x y ]) z ]
    
  • Identity - "./." is the neutral element for normalised paths:

    subpath.join [ ] == "./."
    subpath.join [ (subpath.normalise p) "./." ] == subpath.normalise p
    subpath.join [ "./." (subpath.normalise p) ] == subpath.normalise p
    
  • Normalisation - the result is normalised:

    subpath.join ps == subpath.normalise (subpath.join ps)
    
  • For non-empty lists, the implementation is equivalent to normalising the result of concatStringsSep "/". Note that the above laws can be derived from this one:

    ps != [] -> subpath.join ps == subpath.normalise (concatStringsSep "/" ps)
    
Inputs
subpaths

The list of subpaths to join together

Type
subpath.join :: [String] -> String
Examples
Example 237. subpath.join usage example
subpath.join [ "foo" "bar/baz" ]
=> "./foo/bar/baz"

# normalise the result
subpath.join [ "./foo" "." "bar//./baz/" ]
=> "./foo/bar/baz"

# passing an empty list results in the current directory
subpath.join [ ]
=> "./."

# elements must be valid subpath strings
subpath.join [ /foo ]
=> <error>
subpath.join [ "" ]
=> <error>
subpath.join [ "/foo" ]
=> <error>
subpath.join [ "../foo" ]
=> <error>

Located at lib/path/default.nix:642 in <nixpkgs>.

lib.path.subpath.components

Split a subpath into its path component strings. Throw an error if the subpath isn’t valid. Note that the returned path components are also valid subpath strings, though they are intentionally not normalised.

Laws:

  • Splitting a subpath into components and joining the components gives the same subpath but normalised:

    subpath.join (subpath.components s) == subpath.normalise s
    
Inputs
subpath

The subpath string to split into components

Type
subpath.components :: String -> [String]
Examples
Example 238. subpath.components usage example
subpath.components "."
=> [ ]

subpath.components "./foo//bar/./baz/"
=> [ "foo" "bar" "baz" ]

subpath.components "/foo"
=> <error>

Located at lib/path/default.nix:702 in <nixpkgs>.

lib.path.subpath.normalise

Normalise a subpath. Throw an error if the subpath isn’t valid.

  • Limit repeating / to a single one.

  • Remove redundant . components.

  • Remove trailing / and /..

  • Add leading ./.

Laws:

  • Idempotency - normalising multiple times gives the same result:

    subpath.normalise (subpath.normalise p) == subpath.normalise p
    
  • Uniqueness - there’s only a single normalisation for the paths that lead to the same file system node:

    subpath.normalise p != subpath.normalise q -> $(realpath ${p}) != $(realpath ${q})
    
  • Don’t change the result when appended to a Nix path value:

    append base p == append base (subpath.normalise p)
    
  • Don’t change the path according to realpath:

    $(realpath ${p}) == $(realpath ${subpath.normalise p})
    
  • Only error on invalid subpaths:

    builtins.tryEval (subpath.normalise p)).success == subpath.isValid p
    
Inputs
subpath

The subpath string to normalise

Type
subpath.normalise :: String -> String
Examples
Example 239. subpath.normalise usage example
# limit repeating `/` to a single one
subpath.normalise "foo//bar"
=> "./foo/bar"

# remove redundant `.` components
subpath.normalise "foo/./bar"
=> "./foo/bar"

# add leading `./`
subpath.normalise "foo/bar"
=> "./foo/bar"

# remove trailing `/`
subpath.normalise "foo/bar/"
=> "./foo/bar"

# remove trailing `/.`
subpath.normalise "foo/bar/."
=> "./foo/bar"

# Return the current directory as `./.`
subpath.normalise "."
=> "./."

# error on `..` path components
subpath.normalise "foo/../bar"
=> <error>

# error on empty string
subpath.normalise ""
=> <error>

# error on absolute path
subpath.normalise "/foo"
=> <error>

Located at lib/path/default.nix:799 in <nixpkgs>.

lib.fetchers: functions which can be reused across fetchers

lib.fetchers.normalizeHash

Converts an attrset containing one of hash, sha256 or sha512, into one containing outputHash{,Algo} as accepted by mkDerivation.

An appropriate “fake hash” is substituted when the hash value is "", as is the convention for fetchers.

All other attributes in the set remain as-is.

Type
normalizeHash :: { hashTypes :: [String]; required :: Bool; } -> AttrSet -> AttrSet
Arguments
hashTypes

the set of attribute names accepted as hash inputs, in addition to hash

required

whether to throw if no hash was present in the input; otherwise returns the original input, unmodified

Example
Example 240. lib.fetchers.normalizeHash usage example
normalizeHash { } { hash = ""; foo = "bar"; }
=>
{
  outputHash = lib.fakeHash;
  outputHashAlgo = null;
  foo = "bar";
}
normalizeHash { } { sha256 = lib.fakeSha256; }
=>
{
  outputHash = lib.fakeSha256;
  outputHashAlgo = "sha256";
}
normalizeHash { } { sha512 = lib.fakeSha512; }
=>
{
  outputHash = lib.fakeSha512;
  outputHashAlgo = "sha512";
}

Located at lib/fetchers.nix:113 in <nixpkgs>.

lib.fetchers.withNormalizedHash

Wraps a function which accepts outputHash{,Algo} into one which accepts hash or sha{256,512}

Example
withNormalizedHash { hashTypes = [ "sha256" "sha512" ]; } (
  { outputHash, outputHashAlgo, ... }:
  ...
)

is a function which accepts one of hash, sha256, or sha512 (or the original’s outputHash and outputHashAlgo).

Its functionArgs metadata only lists hash as a parameter, optional iff. outputHash was an optional parameter of the original function. sha256, sha512, outputHash, or outputHashAlgo are not mentioned in the functionArgs metadata.

Type
withNormalizedHash :: { hashTypes :: [String]; } -> (AttrSet -> a) -> (AttrSet -> a)
Arguments
hashTypes

the set of attribute names accepted as hash inputs, in addition to hash

they must correspond to a valid value for outputHashAlgo, currently one of: md5, sha1, sha256, or sha512.

f

the function to be wrapped

Note

In nixpkgs, mkDerivation rejects MD5 outputHashes, and SHA-1 is being deprecated.

As such, there is no reason to add md5 to hashTypes, and sha1 should only ever be included for backwards compatibility.

Output

withNormalizedHash { inherit hashTypes; } f is functionally equivalent to

args: f (normalizeHash {
  inherit hashTypes;
  required = !(lib.functionArgs f).outputHash;
} args)

However, withNormalizedHash preserves functionArgs metadata insofar as possible, and is implemented somewhat more efficiently.

Located at lib/fetchers.nix:201 in <nixpkgs>.

lib.filesystem: filesystem functions

Functions for querying information about the filesystem without copying any files to the Nix store.

lib.filesystem.pathType

The type of a path. The path needs to exist and be accessible. The result is either "directory" for a directory, "regular" for a regular file, "symlink" for a symlink, or "unknown" for anything else.

Inputs
path

The path to query

Type
pathType :: Path -> String
Examples
Example 241. lib.filesystem.pathType usage example
pathType /.
=> "directory"

pathType /some/file.nix
=> "regular"

Located at lib/filesystem.nix:69 in <nixpkgs>.

lib.filesystem.pathIsDirectory

Whether a path exists and is a directory.

Inputs
path

1. Function argument

Type
pathIsDirectory :: Path -> Bool
Examples
Example 242. lib.filesystem.pathIsDirectory usage example
pathIsDirectory /.
=> true

pathIsDirectory /this/does/not/exist
=> false

pathIsDirectory /some/file.nix
=> false

Located at lib/filesystem.nix:103 in <nixpkgs>.

lib.filesystem.pathIsRegularFile

Whether a path exists and is a regular file, meaning not a symlink or any other special file type.

Inputs
path

1. Function argument

Type
pathIsRegularFile :: Path -> Bool
Examples
Example 243. lib.filesystem.pathIsRegularFile usage example
pathIsRegularFile /.
=> false

pathIsRegularFile /this/does/not/exist
=> false

pathIsRegularFile /some/file.nix
=> true

Located at lib/filesystem.nix:137 in <nixpkgs>.

lib.filesystem.haskellPathsInDir

A map of all haskell packages defined in the given path, identified by having a cabal file with the same name as the directory itself.

Inputs
root

The directory within to search

Type
haskellPathsInDir :: Path -> { [String] :: Path }

Located at lib/filesystem.nix:156 in <nixpkgs>.

lib.filesystem.locateDominatingFile

Find the first directory containing a file matching pattern upward from a given file. Returns null if no directories contain a file matching pattern.

Inputs
pattern

The pattern to search for

file

The file to start searching upward from

Type
locateDominatingFile :: RegExp -> Path -> ({ path :: Path; matches :: [MatchResults]; } | Null)

Located at lib/filesystem.nix:193 in <nixpkgs>.

lib.filesystem.listFilesRecursive

Given a directory, return a flattened list of all files within it recursively.

Inputs
dir

The path to recursively list

Type
listFilesRecursive :: Path -> [Path]

Located at lib/filesystem.nix:233 in <nixpkgs>.

lib.filesystem.packagesFromDirectoryRecursive

Transform a directory tree containing package files suitable for callPackage into a matching nested attribute set of derivations.

For a directory tree like this:

my-packages
├── a.nix
├── b.nix
├── c
│  ├── my-extra-feature.patch
│  ├── package.nix
│  └── support-definitions.nix
└── my-namespace
   ├── d.nix
   ├── e.nix
   └── f
      └── package.nix

packagesFromDirectoryRecursive will produce an attribute set like this:

# packagesFromDirectoryRecursive {
#   callPackage = pkgs.callPackage;
#   directory = ./my-packages;
# }
{
  a = pkgs.callPackage ./my-packages/a.nix { };
  b = pkgs.callPackage ./my-packages/b.nix { };
  c = pkgs.callPackage ./my-packages/c/package.nix { };
  my-namespace = {
    d = pkgs.callPackage ./my-packages/my-namespace/d.nix { };
    e = pkgs.callPackage ./my-packages/my-namespace/e.nix { };
    f = pkgs.callPackage ./my-packages/my-namespace/f/package.nix { };
  };
}

In particular:

  • If the input directory contains a package.nix file, then callPackage <directory>/package.nix { } is returned.

  • Otherwise, the input directory’s contents are listed and transformed into an attribute set.

    • If a regular file’s name has the .nix extension, it is turned into attribute where:

      • The attribute name is the file name without the .nix extension

      • The attribute value is callPackage <file path> { }

    • Directories are turned into an attribute where:

      • The attribute name is the name of the directory

      • The attribute value is the result of calling packagesFromDirectoryRecursive { ... } on the directory.

      As a result, directories with no .nix files (including empty directories) will be transformed into empty attribute sets.

    • Other files are ignored, including symbolic links to directories and to regular .nix files; this is because nixlang code cannot distinguish the type of a link’s target.

Inputs
callPackage

The function used to convert a Nix file’s path into a leaf of the attribute set. It is typically the callPackage function, taken from either pkgs or a new scope corresponding to the directory.

newScope

If present, this function is used when recursing into a directory, to generate a new scope. The arguments are updated with the scope’s callPackage and newScope functions, so packages can require anything in their scope, or in an ancestor of their scope.

directory

The directory to read package files from.

Type
packagesFromDirectoryRecursive :: {
  callPackage :: Path -> AttrSet -> Any;
  newScope? :: AttrSet -> Scope;
  directory :: Path;
} -> AttrSet
Examples
Example 244. Basic use of lib.packagesFromDirectoryRecursive
packagesFromDirectoryRecursive {
  inherit (pkgs) callPackage;
  directory = ./my-packages;
}
=> { ... }

In this case, callPackage will only search pkgs for a file’s input parameters. In other words, a file cannot refer to another file in the directory in its input parameters.


Example 245. Create a scope for the nix files found in a directory
packagesFromDirectoryRecursive {
  inherit (pkgs) callPackage newScope;
  directory = ./my-packages;
}
=> { ... }

For example, take the following directory structure:

my-packages
├── a.nix    → { b }: assert b ? b1; ...
└── b
   ├── b1.nix  → { a }: ...
   └── b2.nix

Here, b1.nix can specify { a } as a parameter, which callPackage will resolve as expected. Likewise, a.nix receive an attrset corresponding to the contents of the b directory.

Note

a.nix cannot directly take as inputs packages defined in a child directory, such as b1.


Located at lib/filesystem.nix:370 in <nixpkgs>.

lib.filesystem.resolveDefaultNix

Append /default.nix if the passed path is a directory.

Inputs

A single argument which can be a path value or a string containing an absolute path.

Output

If the input refers to a directory that exists, the output is that same path with /default.nix appended. Furthermore, if the input is a string that ends with /, default.nix is appended to it. Otherwise, the input is returned unchanged.

Type
resolveDefaultNix :: (Path | String) -> (Path | String)
Examples
Example 246. lib.filesystem.resolveDefaultNix usage example

This expression checks whether a and b refer to the same locally available Nix file path.

resolveDefaultNix a == resolveDefaultNix b

For instance, if a is /some/dir and b is /some/dir/default.nix, and /some/dir/ exists, the expression evaluates to true, despite a and b being different references to the same Nix file.

Located at lib/filesystem.nix:478 in <nixpkgs>.


lib.fileset: file set functions

The lib.fileset library allows you to work with file sets. A file set is a (mathematical) set of local files that can be added to the Nix store for use in Nix derivations. File sets are easy and safe to use, providing obvious and composable semantics with good error messages to prevent mistakes.

Overview

Basics:

Combinators:

Filtering:

Utilities:

If you need more file set functions, see this issue to request it.

Implicit coercion from paths to file sets

All functions accepting file sets as arguments can also accept paths as arguments. Such path arguments are implicitly coerced to file sets containing all files under that path:

  • A path to a file turns into a file set containing that single file.

  • A path to a directory turns into a file set containing all files recursively in that directory.

If the path points to a non-existent location, an error is thrown.

Note

Just like in Git, file sets cannot represent empty directories. Because of this, a path to a directory that contains no files (recursively) will turn into a file set containing no files.

Note

File set coercion does not add any of the files under the coerced paths to the store. Only the toSource function adds files to the Nix store, and only those files contained in the fileset argument. This is in contrast to using paths in string interpolation, which does add the entire referenced path to the store.

Example

Assume we are in a local directory with a file hierarchy like this:

├─ a/
│  ├─ x (file)
│  └─ b/
│     └─ y (file)
└─ c/
   └─ d/

Here’s a listing of which files get included when different path expressions get coerced to file sets:

  • ./. as a file set contains both a/x and a/b/y (c/ does not contain any files and is therefore omitted).

  • ./a as a file set contains both a/x and a/b/y.

  • ./a/x as a file set contains only a/x.

  • ./a/b as a file set contains only a/b/y.

  • ./c as a file set is empty, since neither c nor c/d contain any files.

lib.fileset.maybeMissing

Create a file set from a path that may or may not exist:

  • If the path does exist, the path is coerced to a file set.

  • If the path does not exist, a file set containing no files is returned.

Inputs
path

1. Function argument

Type
maybeMissing :: Path -> FileSet
Examples
Example 247. lib.fileset.maybeMissing usage example
# All files in the current directory, but excluding main.o if it exists
difference ./. (maybeMissing ./main.o)

Located at lib/fileset/default.nix:186 in <nixpkgs>.

lib.fileset.trace

Incrementally evaluate and trace a file set in a pretty way. This function is only intended for debugging purposes. The exact tracing format is unspecified and may change.

This function takes a final argument to return. In comparison, traceVal returns the given file set argument.

This variant is useful for tracing file sets in the Nix repl.

Inputs
fileset

The file set to trace.

This argument can also be a path, which gets implicitly coerced to a file set.

val

The value to return.

Type
trace :: FileSet -> Any -> Any
Examples
Example 248. lib.fileset.trace usage example
trace (unions [ ./Makefile ./src ./tests/run.sh ]) null
=>
trace: /home/user/src/myProject
trace: - Makefile (regular)
trace: - src (all files in directory)
trace: - tests
trace:   - run.sh (regular)
null

Located at lib/fileset/default.nix:245 in <nixpkgs>.

lib.fileset.traceVal

Incrementally evaluate and trace a file set in a pretty way. This function is only intended for debugging purposes. The exact tracing format is unspecified and may change.

This function returns the given file set. In comparison, trace takes another argument to return.

This variant is useful for tracing file sets passed as arguments to other functions.

Inputs
fileset

The file set to trace and return.

This argument can also be a path, which gets implicitly coerced to a file set.

Type
traceVal :: FileSet -> FileSet
Examples
Example 249. lib.fileset.traceVal usage example
toSource {
  root = ./.;
  fileset = traceVal (unions [
    ./Makefile
    ./src
    ./tests/run.sh
  ]);
}
=>
trace: /home/user/src/myProject
trace: - Makefile (regular)
trace: - src (all files in directory)
trace: - tests
trace:   - run.sh (regular)
"/nix/store/...-source"

Located at lib/fileset/default.nix:303 in <nixpkgs>.

lib.fileset.toSource

Add the local files contained in fileset to the store as a single store path rooted at root.

The result is the store path as a string-like value, making it usable e.g. as the src of a derivation, or in string interpolation:

stdenv.mkDerivation {
  src = lib.fileset.toSource { ... };
  # ...
}

The name of the store path is always source.

Inputs

Takes an attribute set with the following attributes

root (Path; required)

The local directory path that will correspond to the root of the resulting store path. Paths in strings, including Nix store paths, cannot be passed as root. root has to be a directory.

Note

Changing root only affects the directory structure of the resulting store path, it does not change which files are added to the store. The only way to change which files get added to the store is by changing the fileset attribute.

fileset (FileSet; required)

The file set whose files to import into the store. File sets can be created using other functions in this library. This argument can also be a path, which gets implicitly coerced to a file set.

Note

If a directory does not recursively contain any file, it is omitted from the store path contents.

Type
toSource :: {
  root :: Path,
  fileset :: FileSet,
} -> SourceLike
Examples
Example 250. lib.fileset.toSource usage example
# Import the current directory into the store
# but only include files under ./src
toSource {
  root = ./.;
  fileset = ./src;
}
=> "/nix/store/...-source"

# Import the current directory into the store
# but only include ./Makefile and all files under ./src
toSource {
  root = ./.;
  fileset = union
    ./Makefile
    ./src;
}
=> "/nix/store/...-source"

# Trying to include a file outside the root will fail
toSource {
  root = ./.;
  fileset = unions [
    ./Makefile
    ./src
    ../LICENSE
  ];
}
=> <error>

# The root needs to point to a directory that contains all the files
toSource {
  root = ../.;
  fileset = unions [
    ./Makefile
    ./src
    ../LICENSE
  ];
}
=> "/nix/store/...-source"

# The root has to be a local filesystem path
toSource {
  root = "/nix/store/...-source";
  fileset = ./.;
}
=> <error>

Located at lib/fileset/default.nix:418 in <nixpkgs>.

lib.fileset.toList

The list of file paths contained in the given file set.

Note

This function is strict in the entire file set. This is in contrast with combinators lib.fileset.union, lib.fileset.intersection and lib.fileset.difference.

Thus it is recommended to call toList on file sets created using the combinators, instead of doing list processing on the result of toList.

The resulting list of files can be turned back into a file set using lib.fileset.unions.

Inputs
fileset

The file set whose file paths to return. This argument can also be a path, which gets implicitly coerced to a file set.

Type
toList :: FileSet -> [ Path ]
Examples
Example 251. lib.fileset.toList usage example
toList ./.
[ ./README.md ./Makefile ./src/main.c ./src/main.h ]

toList (difference ./. ./src)
[ ./README.md ./Makefile ]

Located at lib/fileset/default.nix:512 in <nixpkgs>.

lib.fileset.union

The file set containing all files that are in either of two given file sets. This is the same as unions, but takes just two file sets instead of a list. See also Union (set theory).

The given file sets are evaluated as lazily as possible, with the first argument being evaluated first if needed.

Inputs
fileset1

The first file set. This argument can also be a path, which gets implicitly coerced to a file set.

fileset2

The second file set. This argument can also be a path, which gets implicitly coerced to a file set.

Type
union :: FileSet -> FileSet -> FileSet
Examples
Example 252. lib.fileset.union usage example
# Create a file set containing the file `Makefile`
# and all files recursively in the `src` directory
union ./Makefile ./src

# Create a file set containing the file `Makefile`
# and the LICENSE file from the parent directory
union ./Makefile ../LICENSE

Located at lib/fileset/default.nix:555 in <nixpkgs>.

lib.fileset.unions

The file set containing all files that are in any of the given file sets. This is the same as union, but takes a list of file sets instead of just two. See also Union (set theory).

The given file sets are evaluated as lazily as possible, with earlier elements being evaluated first if needed.

Inputs
filesets

A list of file sets. The elements can also be paths, which get implicitly coerced to file sets.

Type
unions :: [ FileSet ] -> FileSet
Examples
Example 253. lib.fileset.unions usage example
# Create a file set containing selected files
unions [
  # Include the single file `Makefile` in the current directory
  # This errors if the file doesn't exist
  ./Makefile

  # Recursively include all files in the `src/code` directory
  # If this directory is empty this has no effect
  ./src/code

  # Include the files `run.sh` and `unit.c` from the `tests` directory
  ./tests/run.sh
  ./tests/unit.c

  # Include the `LICENSE` file from the parent directory
  ../LICENSE
]

Located at lib/fileset/default.nix:617 in <nixpkgs>.

lib.fileset.intersection

The file set containing all files that are in both of two given file sets. See also Intersection (set theory).

The given file sets are evaluated as lazily as possible, with the first argument being evaluated first if needed.

Inputs
fileset1

The first file set. This argument can also be a path, which gets implicitly coerced to a file set.

fileset2

The second file set. This argument can also be a path, which gets implicitly coerced to a file set.

Type
intersection :: FileSet -> FileSet -> FileSet
Examples
Example 254. lib.fileset.intersection usage example
# Limit the selected files to the ones in ./., so only ./src and ./Makefile
intersection ./. (unions [ ../LICENSE ./src ./Makefile ])

Located at lib/fileset/default.nix:668 in <nixpkgs>.

lib.fileset.difference

The file set containing all files from the first file set that are not in the second file set. See also Difference (set theory).

The given file sets are evaluated as lazily as possible, with the first argument being evaluated first if needed.

Inputs
positive

The positive file set. The result can only contain files that are also in this file set. This argument can also be a path, which gets implicitly coerced to a file set.

negative

The negative file set. The result will never contain files that are also in this file set. This argument can also be a path, which gets implicitly coerced to a file set.

Type
difference :: FileSet -> FileSet -> FileSet
Examples
Example 255. lib.fileset.difference usage example
# Create a file set containing all files from the current directory,
# except ones under ./tests
difference ./. ./tests

let
  # A set of Nix-related files
  nixFiles = unions [ ./default.nix ./nix ./tests/default.nix ];
in
# Create a file set containing all files under ./tests, except ones in `nixFiles`,
# meaning only without ./tests/default.nix
difference ./tests nixFiles

Located at lib/fileset/default.nix:727 in <nixpkgs>.

lib.fileset.fileFilter

Filter a file set to only contain files matching some predicate.

Inputs
predicate

The predicate function to call on all files contained in given file set. A file is included in the resulting file set if this function returns true for it.

This function is called with an attribute set containing these attributes:

  • name (String): The name of the file

  • type (String, one of "regular", "symlink" or "unknown"): The type of the file. This matches result of calling builtins.readFileType on the file’s path.

  • hasExt (String -> Bool): Whether the file has a certain file extension. hasExt ext is true only if hasSuffix ".${ext}" name.

    This also means that e.g. for a file with name .gitignore, hasExt "gitignore" is true.

Other attributes may be added in the future.

path

The path whose files to filter

Type
fileFilter ::
  ({
    name :: String,
    type :: String,
    hasExt :: String -> Bool,
    ...
  } -> Bool)
  -> Path
  -> FileSet
Examples
Example 256. lib.fileset.fileFilter usage example
# Include all regular `default.nix` files in the current directory
fileFilter (file: file.name == "default.nix") ./.

# Include all non-Nix files from the current directory
fileFilter (file: ! file.hasExt "nix") ./.

# Include all files that start with a "." in the current directory
fileFilter (file: hasPrefix "." file.name) ./.

# Include all regular files (not symlinks or others) in the current directory
fileFilter (file: file.type == "regular") ./.

Located at lib/fileset/default.nix:806 in <nixpkgs>.

lib.fileset.fromSource

Create a file set with the same files as a lib.sources-based value. This does not import any of the files into the store.

This can be used to gradually migrate from lib.sources-based filtering to lib.fileset.

A file set can be turned back into a source using toSource.

Note

File sets cannot represent empty directories. Turning the result of this function back into a source using toSource will therefore not preserve empty directories.

Inputs
source

1. Function argument

Type
fromSource :: SourceLike -> FileSet
Examples
Example 257. lib.fileset.fromSource usage example
# There's no cleanSource-like function for file sets yet,
# but we can just convert cleanSource to a file set and use it that way
toSource {
  root = ./.;
  fileset = fromSource (lib.sources.cleanSource ./.);
}

# Keeping a previous sourceByRegex (which could be migrated to `lib.fileset.unions`),
# but removing a subdirectory using file set functions
difference
  (fromSource (lib.sources.sourceByRegex ./. [
    "^README\\.md$"
    # This regex includes everything in ./doc
    "^doc(/.*)?$"
  ])
  ./doc/generated

# Use cleanSource, but limit it to only include ./Makefile and files under ./src
intersection
  (fromSource (lib.sources.cleanSource ./.))
  (unions [
    ./Makefile
    ./src
  ]);

Located at lib/fileset/default.nix:880 in <nixpkgs>.

lib.fileset.gitTracked

Create a file set containing all Git-tracked files in a repository.

This function behaves like gitTrackedWith { } - using the defaults.

Inputs
path

The path to the working directory of a local Git repository. This directory must contain a .git file or subdirectory.

Type
gitTracked :: Path -> FileSet
Examples
Example 258. lib.fileset.gitTracked usage example
# Include all files tracked by the Git repository in the current directory
gitTracked ./.

# Include only files tracked by the Git repository in the parent directory
# that are also in the current directory
intersection ./. (gitTracked ../.)

Located at lib/fileset/default.nix:939 in <nixpkgs>.

lib.fileset.gitTrackedWith

Create a file set containing all Git-tracked files in a repository. The first argument allows configuration with an attribute set, while the second argument is the path to the Git working tree.

gitTrackedWith does not perform any filtering when the path is a Nix store path and not a repository. In this way, it accommodates the use case where the expression that makes the gitTracked call does not reside in an actual git repository anymore, and has presumably already been fetched in a way that excludes untracked files. Fetchers with such equivalent behavior include builtins.fetchGit, builtins.fetchTree (experimental), and pkgs.fetchgit when used without leaveDotGit.

If you don’t need the configuration, you can use gitTracked instead.

This is equivalent to the result of unions on all files returned by git ls-files (which uses --cached by default).

Warning

Currently this function is based on builtins.fetchGit As such, this function causes all Git-tracked files to be unnecessarily added to the Nix store, without being re-usable by toSource.

This may change in the future.

Inputs
options (attribute set)
recurseSubmodules (optional, default: false)

Whether to recurse into Git submodules to also include their tracked files. If true, this is equivalent to passing the –recurse-submodules flag to git ls-files.

path

The path to the working directory of a local Git repository. This directory must contain a .git file or subdirectory.

Type
gitTrackedWith :: { recurseSubmodules :: Bool ? false } -> Path -> FileSet
Examples
Example 259. lib.fileset.gitTrackedWith usage example
# Include all files tracked by the Git repository in the current directory
# and any submodules under it
gitTracked { recurseSubmodules = true; } ./.

Located at lib/fileset/default.nix:994 in <nixpkgs>.

lib.fileset.empty

The empty fileset. It can be useful as a default value or as starting accumulator for a folding operation.

Type
empty :: FileSet

Located at lib/fileset/default.nix:1017 in <nixpkgs>.

lib.fileset.isFileset

Tests whether a given value is a fileset, or can be used in place of a fileset.

Inputs
value

The value to test

Type
isFileset :: Any -> Bool
Examples
Example 260. lib.fileset.isFileset usage example
isFileset ./.
=> true

isFileset (unions [  ])
=> true

isFileset 1
=> false

Located at lib/fileset/default.nix:1051 in <nixpkgs>.

lib.sources: source filtering functions

lib.sources.commitIdFromGitRepo

Get the commit id of a git repo.

Inputs
path

1. Function argument

Examples
Example 261. commitIdFromGitRepo usage example
commitIdFromGitRepo <nixpkgs/.git>

Located at lib/sources.nix:520 in <nixpkgs>.

lib.sources.cleanSource

Filters a source tree removing version control files and directories using cleanSourceFilter.

Inputs
src

1. Function argument

Examples
Example 262. cleanSource usage example
cleanSource ./.

Located at lib/sources.nix:522 in <nixpkgs>.

lib.sources.cleanSourceWith

Like builtins.filterSource, except it will compose with itself, allowing you to chain multiple calls together without any intermediate copies being put in the nix store.

Examples
Example 263. cleanSourceWith usage example
lib.cleanSourceWith {
  filter = f;
  src = lib.cleanSourceWith {
    filter = g;
    src = ./.;
  };
}
# Succeeds!

builtins.filterSource f (builtins.filterSource g ./.)
# Fails!

Located at lib/sources.nix:523 in <nixpkgs>.

lib.sources.cleanSourceFilter

A basic filter for cleanSourceWith that removes directories of version control system, backup files (*~) and some generated files.

Inputs
name

1. Function argument

type

2. Function argument

Located at lib/sources.nix:524 in <nixpkgs>.

lib.sources.sourceByRegex

Filter sources by a list of regular expressions.

Inputs
src

1. Function argument

regexes

2. Function argument

Examples
Example 264. sourceByRegex usage example
src = sourceByRegex ./my-subproject [".*\\.py$" "^database\\.sql$"]

Located at lib/sources.nix:533 in <nixpkgs>.

lib.sources.sourceFilesBySuffices

Get all files ending with the specified suffices from the given source directory or its descendants, omitting files that do not match any suffix. The result of the example below will include files like ./dir/module.c and ./dir/subdir/doc.xml if present.

Inputs
src

Path or source containing the files to be returned

exts

A list of file suffix strings

Type
sourceFilesBySuffices :: SourceLike -> [String] -> Source
Examples
Example 265. sourceFilesBySuffices usage example
sourceFilesBySuffices ./. [ ".xml" ".c" ]

Located at lib/sources.nix:534 in <nixpkgs>.

lib.sources.trace

Add logging to a source, for troubleshooting the filtering behavior.

Inputs
src

Source to debug. The returned source will behave like this source, but also log its filter invocations.

Type
sources.trace :: SourceLike -> Source

Located at lib/sources.nix:536 in <nixpkgs>.

lib.cli: command-line serialization functions

lib.cli.toGNUCommandLineShell

Automatically convert an attribute set to command-line options.

This helps protect against malformed command lines and also to reduce boilerplate related to command-line construction for simple use cases.

toGNUCommandLineShell returns an escaped shell string.

Inputs
options

How to format the arguments, see toGNUCommandLine

attrs

The attributes to transform into arguments.

Examples
Example 266. lib.cli.toGNUCommandLineShell usage example
cli.toGNUCommandLineShell {} {
  data = builtins.toJSON { id = 0; };
  X = "PUT";
  retry = 3;
  retry-delay = null;
  url = [ "https://example.com/foo" "https://example.com/bar" ];
  silent = false;
  verbose = true;
}
=> "'-X' 'PUT' '--data' '{\"id\":0}' '--retry' '3' '--url' 'https://example.com/foo' '--url' 'https://example.com/bar' '--verbose'";

Located at lib/cli.nix:42 in <nixpkgs>.

lib.cli.toGNUCommandLine

Automatically convert an attribute set to a list of command-line options.

toGNUCommandLine returns a list of string arguments.

Inputs
options

How to format the arguments, see below.

attrs

The attributes to transform into arguments.

Options
mkOptionName

How to string-format the option name; By default one character is a short option (-), more than one characters a long option (--).

mkBool

How to format a boolean value to a command list; By default it’s a flag option (only the option name if true, left out completely if false).

mkList

How to format a list value to a command list; By default the option name is repeated for each value and mkOption is applied to the values themselves.

mkOption

How to format any remaining value to a command list; On the toplevel, booleans and lists are handled by mkBool and mkList, though they can still appear as values of a list. By default, everything is printed verbatim and complex types are forbidden (lists, attrsets, functions). null values are omitted.

optionValueSeparator

How to separate an option from its flag; By default, there is no separator, so option -c and value 5 would become ["-c" "5"]. This is useful if the command requires equals, for example, -c=5.

Examples
Example 267. lib.cli.toGNUCommandLine usage example
cli.toGNUCommandLine {} {
  data = builtins.toJSON { id = 0; };
  X = "PUT";
  retry = 3;
  retry-delay = null;
  url = [ "https://example.com/foo" "https://example.com/bar" ];
  silent = false;
  verbose = true;
}
=> [
  "-X" "PUT"
  "--data" "{\"id\":0}"
  "--retry" "3"
  "--url" "https://example.com/foo"
  "--url" "https://example.com/bar"
  "--verbose"
]

Located at lib/cli.nix:118 in <nixpkgs>.

lib.cli.toCommandLineShellGNU

Converts the given attributes into a single shell-escaped command-line string. Similar to toCommandLineGNU, but returns a single escaped string instead of a list of arguments. For further reference see: lib.cli.toCommandLineGNU

Located at lib/cli.nix:166 in <nixpkgs>.

lib.cli.toCommandLineGNU

Converts an attribute set into a list of GNU-style command-line arguments.

toCommandLineGNU returns a list of string arguments.

Inputs
options

Options, see below.

attrs

The attributes to transform into arguments.

Options
isLong

A function that determines whether an option is long or short.

explicitBool

Whether or not boolean option arguments should be formatted explicitly.

formatArg

A function that turns the option argument into a string.

Examples
Example 268. lib.cli.toCommandLineGNU usage example
lib.cli.toCommandLineGNU {} {
  v = true;
  verbose = [true true false null];
  i = ".bak";
  testsuite = ["unit" "integration"];
  e = ["s/a/b/" "s/b/c/"];
  n = false;
  data = builtins.toJSON {id = 0;};
}
=> [
  "--data={\"id\":0}"
  "-es/a/b/"
  "-es/b/c/"
  "-i.bak"
  "--testsuite=unit"
  "--testsuite=integration"
  "-v"
  "--verbose"
  "--verbose"
]

Located at lib/cli.nix:228 in <nixpkgs>.

lib.cli.toCommandLineShell

Converts the given attributes into a single shell-escaped command-line string. Similar to toCommandLine, but returns a single escaped string instead of a list of arguments. For further reference see: lib.cli.toCommandLine

Located at lib/cli.nix:251 in <nixpkgs>.

lib.cli.toCommandLine

Converts an attribute set into a list of command-line arguments.

This is the most general command-line construction helper in lib.cli. It is parameterized by an optionFormat function, which defines how each option name and its value are rendered.

All other helpers in this file are thin wrappers around this function.

toCommandLine returns a flat list of strings, suitable for use as argv arguments or for further processing (e.g. shell escaping).

Inputs
optionFormat

A function that takes the option name and returns an option spec, where the option spec is an attribute set describing how the option should be rendered.

The returned attribute set must contain:

  • option (string): The option flag itself, e.g. "-v" or "--verbose".

  • sep (string or null): How to separate the option from its argument. If null, the option and its argument are returned as two separate list elements. If a string (e.g. "="), the option and argument are concatenated.

  • explicitBool (bool): Controls how boolean values are handled:

    • false: true emits only the option flag, false emits nothing.

    • true: both true and false are rendered as explicit arguments via formatArg.

Optional fields:

  • formatArg: Converts the option value to a string. Defaults to lib.generators.mkValueStringDefault { }.

attrs

An attribute set mapping option names to values.

Supported value types:

  • null: omitted entirely

  • bool: handled according to explicitBool

  • list: each element is rendered as a separate occurrence of the option

  • any other value: rendered as a single option argument

Empty attribute names are rejected.

Examples
Example 269. lib.cli.toCommandLine basic usage example
let
  optionFormat = optionName: {
    option = "-${optionName}";
    sep = "=";
    explicitBool = true;
  };
in
lib.cli.toCommandLine optionFormat {
  v = true;
  verbose = [
    true
    true
    false
    null
  ];
  i = ".bak";
  testsuite = [
    "unit"
    "integration"
  ];
  e = [
    "s/a/b/"
    "s/b/c/"
  ];
  n = false;
  data = builtins.toJSON { id = 0; };
}
=> [
  "-data={\"id\":0}"
  "-e=s/a/b/"
  "-e=s/b/c/"
  "-i=.bak"
  "-n=false"
  "-testsuite=unit"
  "-testsuite=integration"
  "-v=true"
  "-verbose=true"
  "-verbose=true"
  "-verbose=false"
]

Example 270. lib.cli.toCommandLine usage with a more complex option format
let
  optionFormat =
    optionName:
    let
      isLong = builtins.stringLength optionName > 1;
    in
    {
      option = if isLong then "--${optionName}" else "-${optionName}";
      sep = if isLong then "=" else null;
      explicitBool = true;
      formatArg =
        value:
        if builtins.isAttrs value then
          builtins.toJSON value
        else
          lib.generators.mkValueStringDefault { } value;
    };
in
lib.cli.toCommandLine optionFormat {
  v = true;
  verbose = [
    true
    true
    false
    null
  ];
  n = false;
  output = "result.txt";
  testsuite = [
    "unit"
    "integration"
  ];
  data = {
    id = 0;
    name = "test";
  };
}
=> [
  "--data={\"id\":0,\"name\":\"test\"}"
  "-n"
  "false"
  "--output=result.txt"
  "--testsuite=unit"
  "--testsuite=integration"
  "-v"
  "true"
  "--verbose=true"
  "--verbose=true"
  "--verbose=false"
]

See also
  • lib.cli.toCommandLineShell

  • lib.cli.toCommandLineGNU

  • lib.cli.toCommandLineShellGNU

Located at lib/cli.nix:423 in <nixpkgs>.

lib.generators: functions that create file formats from nix data structures

Functions that generate widespread file formats from nix data structures.

They all follow a similar interface:

generator { config-attrs } data

config-attrs are “holes” in the generators with sensible default implementations that can be overwritten. The default implementations are mostly generators themselves, called with their respective default values; they can be reused.

Tests can be found in ./tests/misc.nix

Further Documentation can be found here.

lib.generators.mkValueStringDefault

Convert a value to a sensible default string representation. The builtin toString function has some strange defaults, suitable for bash scripts but not much else.

Inputs
Options

Empty set, there may be configuration options in the future

v

2. Function argument

Located at lib/generators.nix:92 in <nixpkgs>.

lib.generators.mkKeyValueDefault

Generate a line of key k and value v, separated by character sep. If sep appears in k, it is escaped. Helper for syntaxes with different separators.

mkValueString specifies how values should be formatted.

mkKeyValueDefault {} ":" "f:oo" "bar"
> "f\:oo:bar"
Inputs
Structured function argument
mkValueString (optional, default: mkValueStringDefault {})

Function to convert values to strings

sep

2. Function argument

k

3. Function argument

v

4. Function argument

Located at lib/generators.nix:161 in <nixpkgs>.

lib.generators.toKeyValue

Generate a key-value-style config file from an attrset.

Inputs
Structured function argument
mkKeyValue (optional, default: mkKeyValueDefault {} "=")

format a setting line from key and value

listsAsDuplicateKeys (optional, default: false)

allow lists as values for duplicate keys

indent (optional, default: "")

Initial indentation level

Located at lib/generators.nix:186 in <nixpkgs>.

lib.generators.toINI

Generate an INI-style config file from an attrset of sections to an attrset of key-value pairs.

Inputs
Structured function argument
mkSectionName (optional, default: (name: escape [ "[" "]" ] name))

apply transformations (e.g. escapes) to section names

mkKeyValue (optional, default: {} "=")

format a setting line from key and value

listsAsDuplicateKeys (optional, default: false)

allow lists as values for duplicate keys

Examples
Example 271. lib.generators.toINI usage example
generators.toINI {} {
  foo = { hi = "${pkgs.hello}"; ciao = "bar"; };
  baz = { "also, integers" = 42; };
}

> [baz]
> also, integers=42
>
> [foo]
> ciao=bar
> hi=/nix/store/y93qql1p5ggfnaqjjqhxcw0vqw95rlz0-hello-2.10

The mk* configuration attributes can generically change the way sections and key-value strings are generated.

For more examples see the test cases in ./tests/misc.nix.


Located at lib/generators.nix:244 in <nixpkgs>.

lib.generators.toINIWithGlobalSection

Generate an INI-style config file from an attrset specifying the global section (no header), and an attrset of sections to an attrset of key-value pairs.

Inputs
1. Structured function argument
mkSectionName (optional, default: (name: escape [ "[" "]" ] name))

apply transformations (e.g. escapes) to section names

mkKeyValue (optional, default: {} "=")

format a setting line from key and value

listsAsDuplicateKeys (optional, default: false)

allow lists as values for duplicate keys

2. Structured function argument
globalSection (required)

global section key-value pairs

sections (optional, default: {})

attrset of sections to key-value pairs

Examples
Example 272. lib.generators.toINIWithGlobalSection usage example
generators.toINIWithGlobalSection {} {
  globalSection = {
    someGlobalKey = "hi";
  };
  sections = {
    foo = { hi = "${pkgs.hello}"; ciao = "bar"; };
    baz = { "also, integers" = 42; };
}

> someGlobalKey=hi
>
> [baz]
> also, integers=42
>
> [foo]
> ciao=bar
> hi=/nix/store/y93qql1p5ggfnaqjjqhxcw0vqw95rlz0-hello-2.10

The mk* configuration attributes can generically change the way sections and key-value strings are generated.

For more examples see the test cases in ./tests/misc.nix.


If you don’t need a global section, you can also use generators.toINI directly, which only takes the part in sections.

Located at lib/generators.nix:327 in <nixpkgs>.

lib.generators.toGitINI

Generate a git-config file from an attrset.

It has two major differences from the regular INI format:

  1. values are indented with tabs

  2. sections can have sub-sections

Further: git-config examples

Examples
Example 273. lib.generators.toGitINI usage example
generators.toGitINI {
  url."ssh://git@github.com/".insteadOf = "https://github.com";
  user.name = "edolstra";
}

> [url "ssh://git@github.com/"]
>   insteadOf = "https://github.com"
>
> [user]
>   name = "edolstra"

Inputs
attrs

Key-value pairs to be converted to a git-config file. See the git-config documentation for possible values.

Located at lib/generators.nix:381 in <nixpkgs>.

lib.generators.mkDconfKeyValue

mkKeyValueDefault wrapper that handles dconf INI quirks. The main differences of the format is that it requires strings to be quoted.

Located at lib/generators.nix:436 in <nixpkgs>.

lib.generators.toDconfINI

Generates INI in dconf keyfile style. See the GNOME documentation for details.

Located at lib/generators.nix:442 in <nixpkgs>.

lib.generators.withRecursion

Recurses through a Value limited to a certain depth. (depthLimit)

If the depth is exceeded, an error is thrown, unless throwOnDepthLimit is set to false.

Inputs
Structured function argument
depthLimit (required)

If this option is not null, the given value will stop evaluating at a certain depth

throwOnDepthLimit (optional, default: true)

If this option is true, an error will be thrown, if a certain given depth is exceeded

Value

The value to be evaluated recursively

Located at lib/generators.nix:462 in <nixpkgs>.

lib.generators.toPretty

Pretty print a value, akin to builtins.trace.

Should probably be a builtin as well.

The pretty-printed string should be suitable for rendering default values in the NixOS manual. In particular, it should be as close to a valid Nix expression as possible.

Inputs
Structured function argument
allowPrettyValues

If this option is true, attrsets like { __pretty = fn; val = …; } will use fn to convert val to a pretty printed representation. (This means fn is type Val -> String.)

multiline

If this option is true, the output is indented with newlines for attribute sets and lists

indent

Initial indentation level

Value

The value to be pretty printed

Located at lib/generators.nix:523 in <nixpkgs>.

lib.generators.toPlist

Translate a simple Nix expression to Plist notation.

Inputs
Structured function argument
escape (optional, default: false)

If this option is true, XML special characters are escaped in string values and keys

Value

The value to be converted to Plist

Located at lib/generators.nix:627 in <nixpkgs>.

lib.generators.toDhall

Translate a simple Nix expression to Dhall notation.

Note that integers are translated to Integer and never the Natural type.

Inputs
Options

Empty set, there may be configuration options in the future

Value

The value to be converted to Dhall

Located at lib/generators.nix:728 in <nixpkgs>.

lib.generators.toLua

Translate a simple Nix expression to Lua representation with occasional Lua-inlines that can be constructed by mkLuaInline function.

Configuration:

  • multiline - by default is true which results in indented block-like view.

  • indent - initial indent.

  • asBindings - by default generate single value, but with this use attrset to set global vars.

Note

Regardless of multiline parameter there is no trailing newline.

Inputs
Structured function argument
multiline (optional, default: true)

If this option is true, the output is indented with newlines for attribute sets and lists

indent (optional, default: "")

Initial indentation level

asBindings (optional, default: false)

Interpret as variable bindings

Value

The value to be converted to Lua

Type
toLua :: { multiline :: Bool; indent :: String; asBindings :: Bool; } -> Any -> String
Examples
Example 274. lib.generators.toLua usage example
generators.toLua {}
  {
    cmd = [ "typescript-language-server" "--stdio" ];
    settings.workspace.library = mkLuaInline ''vim.api.nvim_get_runtime_file("", true)'';
  }
->
 {
   ["cmd"] = {
     "typescript-language-server",
     "--stdio"
   },
   ["settings"] = {
     ["workspace"] = {
       ["library"] = (vim.api.nvim_get_runtime_file("", true))
     }
   }
 }

Located at lib/generators.nix:810 in <nixpkgs>.

lib.generators.mkLuaInline

Mark string as Lua expression to be inlined when processed by toLua.

Inputs
expr

1. Function argument

Type
mkLuaInline :: String -> { _type = "lua-inline"; expr :: String; }

Located at lib/generators.nix:885 in <nixpkgs>.

lib.gvariant: GVariant formatted string serialization functions

A partial and basic implementation of GVariant formatted strings. See GVariant Format Strings for details.

Warning

This API is not considered fully stable and it might therefore change in backwards incompatible ways without prior notice.

lib.gvariant.isGVariant

Check if a value is a GVariant value

Inputs
v

value to check

Type
isGVariant :: Any -> Bool

Located at lib/gvariant.nix:69 in <nixpkgs>.

lib.gvariant.mkValue

Returns the GVariant value that most closely matches the given Nix value. If no GVariant value can be found unambiguously then error is thrown.

Inputs
v

1. Function argument

Type
mkValue :: Any -> GVariant

Located at lib/gvariant.nix:134 in <nixpkgs>.

lib.gvariant.mkArray

Returns the GVariant array from the given type of the elements and a Nix list.

Inputs
elems

1. Function argument

Type
mkArray :: [Any] -> GVariant
Examples
Example 275. lib.gvariant.mkArray usage example
# Creating a string array
lib.gvariant.mkArray [ "a" "b" "c" ]

Located at lib/gvariant.nix:191 in <nixpkgs>.

lib.gvariant.mkEmptyArray

Returns the GVariant array from the given empty Nix list.

Inputs
elemType

1. Function argument

Type
mkEmptyArray :: GVariantType -> GVariant
Examples
Example 276. lib.gvariant.mkEmptyArray usage example
# Creating an empty string array
lib.gvariant.mkEmptyArray (lib.gvariant.type.string)

Located at lib/gvariant.nix:230 in <nixpkgs>.

lib.gvariant.mkVariant

Returns the GVariant variant from the given Nix value. Variants are containers of different GVariant type.

Inputs
elem

1. Function argument

Type
mkVariant :: Any -> GVariant
Examples
Example 277. lib.gvariant.mkVariant usage example
lib.gvariant.mkArray [
  (lib.gvariant.mkVariant "a string")
  (lib.gvariant.mkVariant (lib.gvariant.mkInt32 1))
]

Located at lib/gvariant.nix:266 in <nixpkgs>.

lib.gvariant.mkDictionaryEntry

Returns the GVariant dictionary entry from the given key and value.

Inputs
name

The key of the entry

value

The value of the entry

Type
mkDictionaryEntry :: String -> Any -> GVariant
Examples
Example 278. lib.gvariant.mkDictionaryEntry usage example
# A dictionary describing an Epiphany’s search provider
[
  (lib.gvariant.mkDictionaryEntry "url" (lib.gvariant.mkVariant "https://duckduckgo.com/?q=%s&t=epiphany"))
  (lib.gvariant.mkDictionaryEntry "bang" (lib.gvariant.mkVariant "!d"))
  (lib.gvariant.mkDictionaryEntry "name" (lib.gvariant.mkVariant "DuckDuckGo"))
]

Located at lib/gvariant.nix:310 in <nixpkgs>.

lib.gvariant.mkMaybe

Returns the GVariant maybe from the given element type.

Inputs
elemType

1. Function argument

elem

2. Function argument

Type
mkMaybe :: GVariantType -> Any -> GVariant

Located at lib/gvariant.nix:341 in <nixpkgs>.

lib.gvariant.mkNothing

Returns the GVariant nothing from the given element type.

Inputs
elemType

1. Function argument

Type
mkNothing :: GVariantType -> GVariant

Located at lib/gvariant.nix:364 in <nixpkgs>.

lib.gvariant.mkJust

Returns the GVariant just from the given Nix value.

Inputs
elem

1. Function argument

Type
mkJust :: Any -> GVariant

Located at lib/gvariant.nix:381 in <nixpkgs>.

lib.gvariant.mkTuple

Returns the GVariant tuple from the given Nix list.

Inputs
elems

1. Function argument

Type
mkTuple :: [Any] -> GVariant

Located at lib/gvariant.nix:403 in <nixpkgs>.

lib.gvariant.mkBoolean

Returns the GVariant boolean from the given Nix bool value.

Inputs
v

1. Function argument

Type
mkBoolean :: Bool -> GVariant

Located at lib/gvariant.nix:429 in <nixpkgs>.

lib.gvariant.mkString

Returns the GVariant string from the given Nix string value.

Inputs
v

1. Function argument

Type
mkString :: String -> GVariant

Located at lib/gvariant.nix:451 in <nixpkgs>.

lib.gvariant.mkObjectpath

Returns the GVariant object path from the given Nix string value.

Inputs
v

1. Function argument

Type
mkObjectpath :: String -> GVariant

Located at lib/gvariant.nix:476 in <nixpkgs>.

lib.gvariant.mkUchar

Returns the GVariant uchar from the given Nix int value.

Type
mkUchar :: Int -> GVariant

Located at lib/gvariant.nix:492 in <nixpkgs>.

lib.gvariant.mkInt16

Returns the GVariant int16 from the given Nix int value.

Type
mkInt16 :: Int -> GVariant

Located at lib/gvariant.nix:503 in <nixpkgs>.

lib.gvariant.mkUint16

Returns the GVariant uint16 from the given Nix int value.

Type
mkUint16 :: Int -> GVariant

Located at lib/gvariant.nix:514 in <nixpkgs>.

lib.gvariant.mkInt32

Returns the GVariant int32 from the given Nix int value.

Inputs
v

1. Function argument

Type
mkInt32 :: Int -> GVariant

Located at lib/gvariant.nix:531 in <nixpkgs>.

lib.gvariant.mkUint32

Returns the GVariant uint32 from the given Nix int value.

Type
mkUint32 :: Int -> GVariant

Located at lib/gvariant.nix:547 in <nixpkgs>.

lib.gvariant.mkInt64

Returns the GVariant int64 from the given Nix int value.

Type
mkInt64 :: Int -> GVariant

Located at lib/gvariant.nix:558 in <nixpkgs>.

lib.gvariant.mkUint64

Returns the GVariant uint64 from the given Nix int value.

Type
mkUint64 :: Int -> GVariant

Located at lib/gvariant.nix:569 in <nixpkgs>.

lib.gvariant.mkDouble

Returns the GVariant double from the given Nix float value.

Inputs
v

1. Function argument

Type
mkDouble :: Float -> GVariant

Located at lib/gvariant.nix:586 in <nixpkgs>.

lib.customisation: Functions to customise (derivation-related) functions, derivations, or attribute sets

lib.customisation.overrideDerivation

overrideDerivation drv f takes a derivation (i.e., the result of a call to the builtin function derivation) and returns a new derivation in which the attributes of the original are overridden according to the function f. The function f is called with the original derivation attributes.

overrideDerivation allows certain “ad-hoc” customisation scenarios (e.g. in ~/.config/nixpkgs/config.nix). For instance, if you want to “patch” the derivation returned by a package function in Nixpkgs to build another version than what the function itself provides.

For another application, see build-support/vm, where this function is used to build arbitrary derivations inside a QEMU virtual machine.

Note that in order to preserve evaluation errors, the new derivation’s outPath depends on the old one’s, which means that this function cannot be used in circular situations when the old derivation also depends on the new one.

You should in general prefer drv.overrideAttrs over this function; see the nixpkgs manual for more information on overriding.

Inputs
drv

1. Function argument

f

2. Function argument

Type
overrideDerivation :: Derivation -> ( Derivation -> AttrSet ) -> Derivation
Examples
Example 279. lib.customisation.overrideDerivation usage example
mySed = overrideDerivation pkgs.gnused (oldAttrs: {
  name = "sed-4.2.2-pre";
  src = fetchurl {
    url = ftp://alpha.gnu.org/gnu/sed/sed-4.2.2-pre.tar.bz2;
    hash = "sha256-MxBJRcM2rYzQYwJ5XKxhXTQByvSg5jZc5cSHEZoB2IY=";
  };
  patches = [];
});

Located at lib/customisation.nix:98 in <nixpkgs>.

lib.customisation.makeOverridable

makeOverridable takes a function from attribute set to attribute set and injects override attribute which can be used to override arguments of the function.

Please refer to documentation on <pkg>.overrideDerivation to learn about overrideDerivation and caveats related to its use.

Inputs
f

1. Function argument

Type
makeOverridable :: (AttrSet -> a) -> AttrSet -> a
Examples
Example 280. lib.customisation.makeOverridable usage example
nix-repl> x = {a, b}: { result = a + b; }

nix-repl> y = lib.makeOverridable x { a = 1; b = 2; }

nix-repl> y
{ override = «lambda»; overrideDerivation = «lambda»; result = 3; }

nix-repl> y.override { a = 10; }
{ override = «lambda»; overrideDerivation = «lambda»; result = 12; }

Located at lib/customisation.nix:151 in <nixpkgs>.

lib.customisation.callPackageWith

Call the package function in the file fn with the required arguments automatically. The function is called with the arguments args, but any missing arguments are obtained from autoArgs. This function is intended to be partially parameterised, e.g.,

callPackage = callPackageWith pkgs;
pkgs = {
  libfoo = callPackage ./foo.nix { };
  libbar = callPackage ./bar.nix { };
};

If the libbar function expects an argument named libfoo, it is automatically passed as an argument. Overrides or missing arguments can be supplied in args, e.g.

libbar = callPackage ./bar.nix {
  libfoo = null;
  enableX11 = true;
};
Inputs
autoArgs

1. Function argument

fn

2. Function argument

args

3. Function argument

Type
callPackageWith :: AttrSet -> ((AttrSet -> a) | Path) -> AttrSet -> a

Located at lib/customisation.nix:266 in <nixpkgs>.

lib.customisation.callPackagesWith

Like callPackage, but for a function that returns an attribute set of derivations. The override function is added to the individual attributes.

Inputs
autoArgs

1. Function argument

fn

2. Function argument

args

3. Function argument

Type
callPackagesWith :: AttrSet -> ((AttrSet -> AttrSet) | Path) -> AttrSet -> AttrSet

Located at lib/customisation.nix:356 in <nixpkgs>.

lib.customisation.extendDerivation

Add attributes to each output of a derivation without changing the derivation itself and check a given condition when evaluating.

Inputs
condition

1. Function argument

passthru

2. Function argument

drv

3. Function argument

Type
extendDerivation :: Bool -> Any -> Derivation -> Derivation

Located at lib/customisation.nix:399 in <nixpkgs>.

lib.customisation.hydraJob

Strip a derivation of all non-essential attributes, returning only those needed by hydra-eval-jobs. Also strictly evaluate the result to ensure that there are no thunks kept alive to prevent garbage collection.

Inputs
drv

1. Function argument

Type
hydraJob :: (Derivation | Null) -> (Derivation | Null)

Located at lib/customisation.nix:453 in <nixpkgs>.

lib.customisation.makeScope

Make an attribute set (a “scope”) from functions that take arguments from that same attribute set. See Example 281 for how to use it.

Inputs
  1. newScope (AttrSet -> ((AttrSet -> a) | Path) -> AttrSet -> a)

    A function that takes an attribute set attrs and returns what ends up as callPackage in the output.

    Typical values are callPackageWith or the output attribute newScope.

  2. f (AttrSet -> AttrSet)

    A function that takes an attribute set as returned by makeScope newScope f (a “scope”) and returns any attribute set.

    This function is used to compute the fixpoint of the resulting scope using callPackage. Its argument is the lazily evaluated reference to the value of that fixpoint, and is typically called self or final.

    See Example 281 for how to use it. See the section called “lib.fixedPoints: explicit recursion functions” for details on fixpoint computation.

Output

makeScope returns an attribute set of a form called scope, which also contains the final attributes produced by f:

scope :: {
  callPackage :: ((AttrSet -> a) | Path) -> AttrSet -> a
  newScope = AttrSet -> scope
  overrideScope = (scope -> scope -> AttrSet) -> scope
  packages :: AttrSet -> AttrSet
}
  • callPackage (((AttrSet -> a) | Path) -> AttrSet -> a)

    A function that

    1. Takes a function p, or a path to a Nix file that contains a function p, which takes an attribute set and returns value of arbitrary type a,

    2. Takes an attribute set args with explicit attributes to pass to p,

    3. Calls f with attributes from the original attribute set attrs passed to newScope updated with args, i.e. attrs // args, if they match the attributes in the argument of p.

    All such functions p will be called with the same value for attrs.

    See Example 282 for how to use it.

  • newScope (AttrSet -> scope)

    Takes an attribute set attrs and returns a scope that extends the original scope.

  • overrideScope ((scope -> scope -> AttrSet) -> scope)

    Takes a function g of the form final: prev: { # attributes } to act as an overlay on f, and returns a new scope with values determined by extends g f. See for details.

    This allows subsequent modification of the final attribute set in a consistent way, i.e. all functions p invoked with callPackage will be called with the modified values.

  • packages (AttrSet -> AttrSet)

    The value of the argument f to makeScope.

  • final attributes

    The final values returned by f.

Examples
Example 281. Create an interdependent package set on top of pkgs

The functions in foo.nix and bar.nix can depend on each other, in the sense that foo.nix can contain a function that expects bar as an attribute in its argument.

let
  pkgs = import <nixpkgs> { };
in
pkgs.lib.makeScope pkgs.newScope (self: {
  foo = self.callPackage ./foo.nix { };
  bar = self.callPackage ./bar.nix { };
})

evaluates to

{
  callPackage = «lambda»;
  newScope = «lambda»;
  overrideScope = «lambda»;
  packages = «lambda»;
  foo = «derivation»;
  bar = «derivation»;
}

Example 282. Using callPackage from a scope
let
  pkgs = import <nixpkgs> { };
  inherit (pkgs) lib;
  scope = lib.makeScope lib.callPackageWith (self: { a = 1; b = 2; });
  three = scope.callPackage ({ a, b }: a + b) { };
  four = scope.callPackage ({ a, b }: a + b) { a = 2; };
in
[ three four ]

evaluates to

[ 3 4 ]

Type
makeScope :: (AttrSet -> ((AttrSet -> a) | Path) -> AttrSet -> a) -> (AttrSet -> AttrSet) -> Scope

Located at lib/customisation.nix:613 in <nixpkgs>.

lib.customisation.makeScopeWithSplicing

backward compatibility with old uncurried form; deprecated

Inputs
splicePackages

1. Function argument

newScope

2. Function argument

otherSplices

3. Function argument

keep

4. Function argument

extra

5. Function argument

f

6. Function argument

Located at lib/customisation.nix:657 in <nixpkgs>.

lib.customisation.makeScopeWithSplicing'

Like makeScope, but aims to support cross compilation. It’s still ugly, but hopefully it helps a little bit.

Type
makeScopeWithSplicing' ::
  { splicePackages :: Splice -> AttrSet;
    newScope :: AttrSet -> ((AttrSet -> a) | Path) -> AttrSet -> a;
  }
  -> { otherSplices :: Splice; keep :: AttrSet -> AttrSet; extra :: AttrSet -> AttrSet; }
  -> AttrSet

Splice :: {
  pkgsBuildBuild :: AttrSet;
  pkgsBuildHost :: AttrSet;
  pkgsBuildTarget :: AttrSet;
  pkgsHostHost :: AttrSet;
  pkgsHostTarget :: AttrSet;
  pkgsTargetTarget :: AttrSet;
}

Located at lib/customisation.nix:692 in <nixpkgs>.

lib.customisation.extendMkDerivation

Define a mkDerivation-like function based on another mkDerivation-like function.

stdenv.mkDerivation gives access to its final set of derivation attributes when it is passed a function, or when it is passed an overlay-style function in overrideAttrs.

Instead of composing new stdenv.mkDerivation-like build helpers using normal function composition, extendMkDerivation makes sure that the returned build helper supports such first class recursion like mkDerivation does.

extendMkDerivation takes an extra attribute set to configure its behaviour. One can optionally specify transformDrv to specify a function to apply to the result derivation, or inheritFunctionArgs to decide whether to inherit the __functionArgs from the base build helper.

Inputs
extendMkDerivation-specific configurations
constructDrv (required)

Base build helper, the mkDerivation-like build helper to extend.

excludeDrvArgNames (default to [ ])

Argument names not to pass from the input fixed-point arguments to constructDrv. It doesn’t apply to the updating arguments returned by extendDrvArgs.

excludeFunctionArgNames (default to [ ])

__functionArgs attribute names to remove from the result build helper. excludeFunctionArgNames is useful for argument deprecation while avoiding ellipses.

extendDrvArgs (required)

An extension (overlay) of the argument set, like the one taken by overrideAttrs but applied before passing to constructDrv.

inheritFunctionArgs (default to true)

Whether to inherit __functionArgs from the base build helper. Set inheritFunctionArgs to false when extendDrvArgs’s args set pattern does not contain an ellipsis.

transformDrv (default to lib.id)

Function to apply to the result derivation.

Type
extendMkDerivation ::
  {
    constructDrv :: (FixedPointArgs | AttrSet) -> Derivation;
    excludeDrvArgNames :: [String];
    excludeFunctionArgNames :: [String];
    extendDrvArgs :: AttrSet -> AttrSet -> AttrSet;
    inheritFunctionArgs :: Bool;
    transformDrv :: Derivation -> Derivation;
  }
  -> ((FixedPointArgs | AttrSet) -> Derivation)

FixedPointArgs :: AttrSet -> AttrSet
Examples
Example 283. lib.customisation.extendMkDerivation usage example
mkLocalDerivation = lib.extendMkDerivation {
  constructDrv = pkgs.stdenv.mkDerivation;
  excludeDrvArgNames = [ "specialArg" ];
  extendDrvArgs =
    finalAttrs: args@{ preferLocalBuild ? true, allowSubstitute ? false, specialArg ? (_: false), ... }:
    { inherit preferLocalBuild allowSubstitute; passthru = { inherit specialArg; } // args.passthru or { }; };
}

mkLocalDerivation.__functionArgs
=> { allowSubstitute = true; preferLocalBuild = true; specialArg = true; }

mkLocalDerivation { inherit (pkgs.hello) pname version src; specialArg = _: false; }
=> «derivation /nix/store/xirl67m60ahg6jmzicx43a81g635g8z8-hello-2.12.1.drv»

mkLocalDerivation (finalAttrs: { inherit (pkgs.hello) pname version src; specialArg = _: false; })
=> «derivation /nix/store/xirl67m60ahg6jmzicx43a81g635g8z8-hello-2.12.1.drv»

(mkLocalDerivation (finalAttrs: { inherit (pkgs.hello) pname version src; passthru = { foo = "a"; bar = "${finalAttrs.passthru.foo}b"; }; })).bar
=> "ab"

Note

If transformDrv is specified, it should take care of existing attributes that perform overriding (e.g., overrideAttrs) to ensure that the overriding functionality of the result derivation work as expected. Modifications that breaks the overriding include direct attribute set update and lib.extendDerivation.

Located at lib/customisation.nix:843 in <nixpkgs>.

lib.customisation.renameCrossIndexFrom

Removes a prefix from the attribute names of a cross index.

A cross index (short for “Cross Platform Pair Index”) is a 6-field structure organizing values by cross-compilation platform relationships.

Inputs
prefix

The prefix to remove from cross index attribute names

crossIndex

A cross index with prefixed names

Type
renameCrossIndexFrom :: String -> AttrSet -> AttrSet
Examples
Example 284. lib.customisation.renameCrossIndexFrom usage example
renameCrossIndexFrom "pkgs" { pkgsBuildBuild = ...; pkgsBuildHost = ...; ... }
=> { buildBuild = ...; buildHost = ...; ... }

Located at lib/customisation.nix:913 in <nixpkgs>.

lib.customisation.renameCrossIndexTo

Adds a prefix to the attribute names of a cross index.

A cross index (short for “Cross Platform Pair Index”) is a 6-field structure organizing values by cross-compilation platform relationships.

Inputs
prefix

The prefix to add to cross index attribute names

crossIndex

A cross index to be prefixed

Type
renameCrossIndexTo :: String -> AttrSet -> AttrSet
Examples
Example 285. lib.customisation.renameCrossIndexTo usage example
renameCrossIndexTo "self" { buildBuild = ...; buildHost = ...; ... }
=> { selfBuildBuild = ...; selfBuildHost = ...; ... }

Located at lib/customisation.nix:953 in <nixpkgs>.

lib.customisation.mapCrossIndex

Takes a function and applies it pointwise to each field of a cross index.

A cross index (short for “Cross Platform Pair Index”) is a 6-field structure organizing values by cross-compilation platform relationships.

Inputs
f

Function to apply to each cross index value

crossIndex

A cross index to transform

Type
mapCrossIndex :: (a -> b) -> {
  buildBuild :: a;
  buildHost :: a;
  buildTarget :: a;
  hostHost :: a;
  hostTarget :: a;
  targetTarget :: a;
} -> {
  buildBuild :: b;
  buildHost :: b;
  buildTarget :: b;
  hostHost :: b;
  hostTarget :: b;
  targetTarget :: b;
}
Examples
Example 286. lib.customisation.mapCrossIndex usage example
mapCrossIndex (x: x * 10) { buildBuild = 1; buildHost = 2; ... }
=> { buildBuild = 10; buildHost = 20; ... }
# Extract a package from package sets
mapCrossIndex (pkgs: pkgs.hello) crossIndexedPackageSets

Located at lib/customisation.nix:1012 in <nixpkgs>.

lib.meta: functions for derivation metadata

Some functions for manipulating meta attributes, as well as the name attribute.

lib.meta.addMetaAttrs

Add to or override the meta attributes of the given derivation.

Inputs
newAttrs

1. Function argument

drv

2. Function argument

Type
addMetaAttrs :: AttrSet -> Derivation -> Derivation
Examples
Example 287. lib.meta.addMetaAttrs usage example
addMetaAttrs {description = "Bla blah";} somePkg

Located at lib/meta.nix:57 in <nixpkgs>.

lib.meta.dontDistribute

Disable Hydra builds of given derivation.

Inputs
drv

1. Function argument

Type
dontDistribute :: Derivation -> Derivation

Located at lib/meta.nix:81 in <nixpkgs>.

lib.meta.setName

Change the symbolic name of a derivation.

Warning

Dependent derivations will be rebuilt when the symbolic name is changed.

Inputs
name

1. Function argument

drv

2. Function argument

Type
setName :: String -> Derivation -> Derivation

Located at lib/meta.nix:106 in <nixpkgs>.

lib.meta.updateName

Like setName, but takes the previous name as an argument.

Inputs
updater

1. Function argument

drv

2. Function argument

Type
updateName :: (String -> String) -> Derivation -> Derivation
Examples
Example 288. lib.meta.updateName usage example
updateName (oldName: oldName + "-experimental") somePkg

Located at lib/meta.nix:137 in <nixpkgs>.

lib.meta.appendToName

Append a suffix to the name of a package (before the version part).

Inputs
suffix

1. Function argument

Type
appendToName :: String -> Derivation -> Derivation

Located at lib/meta.nix:155 in <nixpkgs>.

lib.meta.mapDerivationAttrset

Apply a function to each derivation and only to derivations in an attrset.

Inputs
f

1. Function argument

set

2. Function argument

Type
mapDerivationAttrset :: (Derivation -> a) -> AttrSet -> AttrSet

Located at lib/meta.nix:184 in <nixpkgs>.

lib.meta.defaultPriority

The default priority of packages in Nix. See defaultPriority in src/nix/profile.cc.

Located at lib/meta.nix:190 in <nixpkgs>.

lib.meta.setPrio

Set the nix-env priority of the package. Note that higher values are lower priority, and vice versa.

Inputs
priority

1. The priority to set.

drv

2. Function argument

Type
setPrio :: Int -> Derivation -> Derivation

Located at lib/meta.nix:209 in <nixpkgs>.

lib.meta.lowPrio

Decrease the nix-env priority of the package, i.e., other versions/variants of the package will be preferred.

Inputs
drv

1. Function argument

Type
lowPrio :: Derivation -> Derivation

Located at lib/meta.nix:227 in <nixpkgs>.

lib.meta.lowPrioSet

Apply lowPrio to an attrset with derivations.

Inputs
set

1. Function argument

Type
lowPrioSet :: { [String] :: Derivation } -> { [String] :: Derivation }

Located at lib/meta.nix:244 in <nixpkgs>.

lib.meta.hiPrio

Increase the nix-env priority of the package, i.e., this version/variant of the package will be preferred.

Inputs
drv

1. Function argument

Type
hiPrio :: Derivation -> Derivation

Located at lib/meta.nix:262 in <nixpkgs>.

lib.meta.hiPrioSet

Apply hiPrio to an attrset with derivations.

Inputs
set

1. Function argument

Type
hiPrioSet :: { [String] :: Derivation } -> { [String] :: Derivation }

Located at lib/meta.nix:279 in <nixpkgs>.

lib.meta.platformMatch

Check to see if a platform is matched by the given meta.platforms element.

A meta.platform pattern is either

  1. (legacy) a system string.

  2. (modern) a pattern for the entire platform structure (see lib.systems.inspect.platformPatterns).

  3. (modern) a pattern for the platform parsed field (see lib.systems.inspect.patterns).

We can inject these into a pattern for the whole of a structured platform, and then match that.

Inputs
platform

1. Function argument

elem

2. Function argument

Examples
Example 289. lib.meta.platformMatch usage example
lib.meta.platformMatch { system = "aarch64-darwin"; } "aarch64-darwin"
=> true

Located at lib/meta.nix:317 in <nixpkgs>.

lib.meta.availableOn

Check if a package is available on a given platform.

A package is available on a platform if both

  1. One of meta.platforms pattern matches the given platform, or meta.platforms is not present.

  2. None of meta.badPlatforms pattern matches the given platform.

Inputs
platform

1. Function argument

pkg

2. Function argument

Examples
Example 290. lib.meta.availableOn usage example
lib.meta.availableOn { system = "aarch64-darwin"; } pkg.zsh
=> true

Located at lib/meta.nix:367 in <nixpkgs>.

lib.meta.licensesSpdx

Mapping of SPDX ID to the attributes in lib.licenses.

For SPDX IDs, see https://spdx.org/licenses. Note that some SPDX licenses might be missing.

Examples
Example 291. lib.meta.licensesSpdx usage example
lib.licensesSpdx.MIT == lib.licenses.mit
=> true
lib.licensesSpdx."MY LICENSE"
=> error: attribute 'MY LICENSE' missing

Located at lib/meta.nix:391 in <nixpkgs>.

lib.meta.getLicenseFromSpdxId

Get the corresponding attribute in lib.licenses from the SPDX ID or warn and fallback to { shortName = <license string>; }.

For SPDX IDs, see https://spdx.org/licenses. Note that some SPDX licenses might be missing.

Type
getLicenseFromSpdxId :: String -> {
  deprecated :: Bool;
  free :: Bool;
  fullName :: String;
  redistributable :: Bool;
  shortName :: String;
  spdxId :: String;
  url :: String;
}
Examples
Example 292. lib.meta.getLicenseFromSpdxId usage example
lib.getLicenseFromSpdxId "MIT" == lib.licenses.mit
=> true
lib.getLicenseFromSpdxId "mIt" == lib.licenses.mit
=> true
lib.getLicenseFromSpdxId "MY LICENSE"
=> trace: warning: getLicenseFromSpdxId: No license matches the given SPDX ID: MY LICENSE
=> { shortName = "MY LICENSE"; }

Located at lib/meta.nix:433 in <nixpkgs>.

lib.meta.getLicenseFromSpdxIdOr

Get the corresponding attribute in lib.licenses from the SPDX ID or fallback to the given default value.

For SPDX IDs, see https://spdx.org/licenses. Note that some SPDX licenses might be missing.

Inputs
licstr

1. SPDX ID string to find a matching license

default

2. Fallback value when a match is not found

Type
getLicenseFromSpdxIdOr :: String -> a -> ({
  deprecated :: Bool;
  free :: Bool;
  fullName :: String;
  redistributable :: Bool;
  shortName :: String;
  spdxId :: String;
  url :: String;
} | a)
Examples
Example 293. lib.meta.getLicenseFromSpdxIdOr usage example
lib.getLicenseFromSpdxIdOr "MIT" null == lib.licenses.mit
=> true
lib.getLicenseFromSpdxId "mIt" null == lib.licenses.mit
=> true
lib.getLicenseFromSpdxIdOr "MY LICENSE" lib.licenses.free == lib.licenses.free
=> true
lib.getLicenseFromSpdxIdOr "MY LICENSE" null
=> null
lib.getLicenseFromSpdxIdOr "MY LICENSE" (throw "No SPDX ID matches MY LICENSE")
=> error: No SPDX ID matches MY LICENSE

Located at lib/meta.nix:489 in <nixpkgs>.

lib.meta.getExe

Get the path to the main program of a package based on meta.mainProgram

Inputs
x

1. Function argument

Type
getExe :: Derivation -> StorePath
Examples
Example 294. lib.meta.getExe usage example
getExe pkgs.hello
=> "/nix/store/g124820p9hlv4lj8qplzxw1c44dxaw1k-hello-2.12/bin/hello"
getExe pkgs.mustache-go
=> "/nix/store/am9ml4f4ywvivxnkiaqwr0hyxka1xjsf-mustache-go-1.3.0/bin/mustache"

Located at lib/meta.nix:526 in <nixpkgs>.

lib.meta.getExe'

Get the path of a program of a derivation.

Inputs
x

1. Function argument

y

2. Function argument

Type
getExe' :: Derivation -> String -> StorePath
Examples
Example 295. lib.meta.getExe' usage example
getExe' pkgs.hello "hello"
=> "/nix/store/g124820p9hlv4lj8qplzxw1c44dxaw1k-hello-2.12/bin/hello"
getExe' pkgs.imagemagick "convert"
=> "/nix/store/5rs48jamq7k6sal98ymj9l4k2bnwq515-imagemagick-7.1.1-15/bin/convert"

Located at lib/meta.nix:572 in <nixpkgs>.

lib.meta.cpeFullVersionWithVendor

Generate CPE parts from inputs. Copies vendor and version to the output, and sets update to *.

Inputs
vendor

package’s vendor

version

package’s version

Type
cpeFullVersionWithVendor :: String -> String -> { update :: String; vendor :: String; version :: String; }
Examples
Example 296. lib.meta.cpeFullVersionWithVendor usage example
lib.meta.cpeFullVersionWithVendor "gnu" "1.2.3"
=> {
  vendor = "gnu";
  version = "1.2.3";
  update = "*";
}

Example 297. lib.meta.cpeFullVersionWithVendor usage in derivations
mkDerivation rec {
  version = "1.2.3";
  # ...
  meta = {
    # ...
    identifiers.cpeParts = lib.meta.cpeFullVersionWithVendor "gnu" version;
  };
}

Located at lib/meta.nix:630 in <nixpkgs>.

lib.derivations: miscellaneous derivation-specific functions

lib.derivations.lazyDerivation

Restrict a derivation to a predictable set of attribute names, so that the returned attrset is not strict in the actual derivation, saving a lot of computation when the derivation is non-trivial.

This is useful in situations where a derivation might only be used for its passthru attributes, improving evaluation performance.

The returned attribute set is lazy in derivation. Specifically, this means that the derivation will not be evaluated in at least the situations below.

For illustration and/or testing, we define derivation such that its evaluation is very noticeable.

let derivation = throw "This won't be evaluated.";

In the following expressions, derivation will not be evaluated:

(lazyDerivation { inherit derivation; }).type

attrNames (lazyDerivation { inherit derivation; })

(lazyDerivation { inherit derivation; } // { foo = true; }).foo

(lazyDerivation { inherit derivation; meta.foo = true; }).meta

In these expressions, derivation will be evaluated:

"${lazyDerivation { inherit derivation }}"

(lazyDerivation { inherit derivation }).outPath

(lazyDerivation { inherit derivation }).meta

And the following expressions are not valid, because the refer to implementation details and/or attributes that may not be present on some derivations:

(lazyDerivation { inherit derivation }).buildInputs

(lazyDerivation { inherit derivation }).passthru

(lazyDerivation { inherit derivation }).pythonPath
Inputs

Takes an attribute set with the following attributes

derivation

The derivation to be wrapped.

meta

Optional meta attribute.

While this function is primarily about derivations, it can improve the meta package attribute, which is usually specified through mkDerivation.

passthru

Optional extra values to add to the returned attrset.

This can be used for adding package attributes, such as tests.

outputs

Optional list of assumed outputs. Default: [ "out" ]

This must match the set of outputs that the returned derivation has. You must use this when the derivation has multiple outputs.

Located at lib/derivations.nix:99 in <nixpkgs>.

lib.derivations.optionalDrvAttr

Conditionally set a derivation attribute.

Because mkDerivation sets __ignoreNulls = true, a derivation attribute set to null will not impact the derivation output hash. Thus, this function passes through its value argument if the cond is true, but returns null if not.

Inputs
cond

Condition

value

Attribute value

Type
optionalDrvAttr :: Bool -> a -> (a | Null)
Examples
Example 298. lib.derivations.optionalDrvAttr usage example
(stdenv.mkDerivation {
  name = "foo";
  x = optionalDrvAttr true 1;
  y = optionalDrvAttr false 1;
}).drvPath == (stdenv.mkDerivation {
  name = "foo";
  x = 1;
}).drvPath
=> true

Located at lib/derivations.nix:219 in <nixpkgs>.

lib.derivations.warnOnInstantiate

Wrap a derivation such that instantiating it produces a warning.

All attributes will be wrapped with lib.warn except from .meta, .name, and .type which are used by nix search, and .outputName which avoids double warnings with nix-instantiate and nix-build.

Inputs
msg

The warning message to emit (via lib.warn).

drv

The derivation to wrap.

Type
warnOnInstantiate :: String -> Derivation -> Derivation
Examples
Example 299. lib.derivations.warnOnInstantiate usage example
{
  myPackage = warnOnInstantiate "myPackage has been renamed to my-package" my-package;
}

Located at lib/derivations.nix:254 in <nixpkgs>.

Generators

Generators are functions that create file formats from Nix data structures, e.g. for configuration files. There are generators available for: INI, JSON and YAML.

All generators follow a similar call interface: generatorName configFunctions data, where configFunctions is an attrset of user-defined functions that format nested parts of the content. They each have common defaults, so often they do not need to be set manually. An example is mkSectionName from the INI generator, which defaults to (name: libStr.escape [ "[" "]" ] name). It receives the name of a section and sanitizes it. The default mkSectionName escapes [ and ] with a backslash.

Generators can be fine-tuned to produce exactly the file format required by your application/service. One example is an INI file format that uses : as a separator, the strings "yes" and "no" as boolean values, and requires all string values to be quoted:

let
  inherit (lib) generators isString;

  customToINI = generators.toINI {
    # specifies how to format a key/value pair
    mkKeyValue = generators.mkKeyValueDefault {
      # specifies the generated string for a subset of nix values
      mkValueString =
        v:
        if v == true then
          ''"yes"''
        else if v == false then
          ''"no"''
        else if isString v then
          ''"${v}"''
        # and delegates all other values to the default generator
        else
          generators.mkValueStringDefault { } v;
    } ":";
  };

  # the INI file can now be given as plain old nix values
in
customToINI {
  main = {
    pushinfo = true;
    autopush = false;
    host = "localhost";
    port = 42;
  };
  mergetool = {
    merge = "diff3";
  };
}

This will produce the following INI file as a Nix string:

[main]
autopush:"no"
host:"localhost"
port:42
pushinfo:"yes"
str\:ange:"very::strange"

[mergetool]
merge:"diff3"

Note

Nix store paths can be converted to strings by enclosing a derivation attribute like so: "${drv}".

Detailed documentation for each generator can be found here

Debugging Nix Expressions

Nix is a unityped, dynamic language, this means any value can potentially appear anywhere. Since it is also non-strict, evaluation order and what is ultimately evaluated might surprise you. Therefore, it is important to be able to debug Nix expressions.

In the lib/debug.nix file you will find a number of functions that help (pretty-)printing values while evaluation is running. You can even specify how deep these values should be printed recursively, and transform them on the fly. Please consult the docstrings in lib/debug.nix for usage information.

prefer-remote-fetch overlay

prefer-remote-fetch is an overlay that downloads sources on a remote builder. This is useful when the evaluating machine has a slow upload while the builder can fetch faster, directly from the source. To use it, put the following snippet as a new overlay:

self: super: (super.prefer-remote-fetch self super)

A full configuration example that sets the overlay up for your own account could look like this

$ mkdir ~/.config/nixpkgs/overlays/
$ cat > ~/.config/nixpkgs/overlays/prefer-remote-fetch.nix <<EOF
  self: super: super.prefer-remote-fetch self super
EOF

pkgs.nix-gitignore

pkgs.nix-gitignore is a function that acts similarly to builtins.filterSource but also allows filtering with the help of the gitignore format.

Usage

pkgs.nix-gitignore exports a number of functions, but you’ll most likely need either gitignoreSource or gitignoreSourcePure. As their first argument, they both accept either 1. a file with gitignore lines or 2. a string with gitignore lines, or 3. a list of either of the two. They will be concatenated into a single big string.

{
  pkgs ? import <nixpkgs> { },
}:
{

  src = nix-gitignore.gitignoreSource [ ] ./source;
  # Simplest version

  src = nix-gitignore.gitignoreSource ''
    supplemental-ignores
  '' ./source;
  # This one reads the ./source/.gitignore and concats the auxiliary ignores

  src = nix-gitignore.gitignoreSourcePure ''
    ignore-this
    ignore-that
  '' ./source;
  # Use this string as gitignore, don't read ./source/.gitignore.

  src = nix-gitignore.gitignoreSourcePure [
    ''
      ignore-this
      ignore-that
    ''
    ~/.gitignore
  ] ./source;
  # It also accepts a list (of strings and paths) that will be concatenated
  # once the paths are turned to strings via readFile.
}

These functions are derived from the Filter functions by setting the first filter argument to (_: _: true):

{
  gitignoreSourcePure = gitignoreFilterSourcePure (_: _: true);
  gitignoreSource = gitignoreFilterSource (_: _: true);
}

Those filter functions accept the same arguments the builtins.filterSource function would pass to its filters, thus fn: gitignoreFilterSourcePure fn "" should be extensionally equivalent to filterSource. The file is blacklisted if it’s blacklisted by either your filter or the gitignoreFilter.

If you want to make your own filter from scratch, you may use

{ gitignoreFilter = ign: root: filterPattern (gitignoreToPatterns ign) root; }

gitignore files in subdirectories

If you wish to use a filter that would search for .gitignore files in subdirectories, just like git does by default, use this function:

{
  # gitignoreFilterRecursiveSource = filter: patterns: root:
  # OR
  gitignoreRecursiveSource = gitignoreFilterSourcePure (_: _: true);
}

Module System

Introduction

The module system is a language for handling configuration, implemented as a Nix library.

Compared to plain Nix, it adds documentation, type checking and composition or extensibility.

Note

This chapter is new and not complete yet.

See also:

  • Introduction to the module system, in the context of NixOS, see Writing NixOS Modules in the NixOS manual.

  • Generic guide to the module system on nix.dev.

lib.evalModules

Evaluate a set of modules. This function is typically only used once per application (e.g. once in NixOS, once in Home Manager, …).

Parameters

modules

A list of modules. These are merged together to form the final configuration.

specialArgs

An attribute set of module arguments that can be used in imports.

This is in contrast to config._module.args, which is only available after all imports have been resolved.

Warning

You may be tempted to use specialArgs.lib to provide extra library functions. Doing so limits the interoperability of modules, as well as the interoperability of Module System applications.

lib is reserved for the Nixpkgs library, and should not be used for custom functions.

Instead, you may create a new attribute in specialArgs to provide custom functions. This clarifies their origin and avoids incompatibilities.

class

If the class attribute is set and non-null, the module system will reject imports with a different _class declaration.

The class value should be a string in lower camel case.

If applicable, the class should match the “prefix” of the attributes used in (experimental) flakes. Some examples are:

  • nixos as in flake.nixosModules

  • nixosTest: modules that constitute a NixOS VM test

prefix

A list of strings representing the location at or below which all options are evaluated. This is used by types.submodule to improve error reporting and find the implicit name module argument.

Return value

The result is an attribute set with the following attributes:

options

The nested attribute set of all option declarations.

config

The nested attribute set of all option values.

type

A module system type. This type is an instance of types.submoduleWith containing the current modules.

The option definitions that are typed with this type will extend the current set of modules, like extendModules.

However, the value returned from the type is just the config, like any submodule.

If you’re familiar with prototype inheritance, you can think of this evalModules invocation as the prototype, and usages of this type as the instances.

This type is also available to the modules as the module argument moduleType.

extendModules

A function similar to evalModules but building on top of the already passed modules. Its arguments, modules and specialArgs are added to the existing values.

If you’re familiar with prototype inheritance, you can think of the current, actual evalModules invocation as the prototype, and the return value of extendModules as the instance.

This functionality is also available to modules as the extendModules module argument.

Note

Evaluation Performance

extendModules returns a configuration that shares very little with the original evalModules invocation, because the module arguments may be different.

So if you have a configuration that has been (or will be) largely evaluated, almost none of the computation is shared with the configuration returned by extendModules.

The real work of module evaluation happens while computing the values in config and options, so multiple invocations of extendModules have a particularly small cost, as long as only the final config and options are evaluated.

If you do reference multiple config (or options) from before and after extendModules, evaluation performance is the same as with multiple evalModules invocations, because the new modules’ ability to override existing configuration fundamentally requires constructing a new config and options fixpoint.

_module

A portion of the configuration tree which is elided from config.

_type

A nominal type marker, always "configuration".

class

The class argument.

graph

Represents all the modules that took part in the evaluation. It is a list of ModuleGraph where ModuleGraph is defined as an attribute set with the following attributes:

  • key: string for the purpose of module deduplication and disabledModules

  • file: string for the purpose of error messages and warnings

  • imports: [ ModuleGraph ]

  • disabled: bool

Module arguments

Module arguments are the attribute values passed to modules when they are evaluated.

They originate from these sources:

  1. Built-in arguments

    • lib,

    • config,

    • options,

    • _class,

    • _prefix,

  2. Attributes from the specialArgs argument passed to evalModules or submoduleWith. These are application-specific.

  3. Attributes from the _module.args option value. These are application-specific and can be provided by any module.

The prior two categories are available while evaluating the imports, whereas the last category is only available after the imports have been resolved.

lib 🔗

A reference to the Nixpkgs library.

config 🔗

All option values. Unlike the evalModules config return attribute, this includes _module.

options 🔗

All evaluated option declarations.

_class 🔗

The expected class of the loaded modules.

_prefix 🔗

The location under which the module is evaluated. This is used to improve error reporting and to find the implicit name module argument in submodules. It is exposed as a module argument due to how the module system is implemented, which cannot be avoided without breaking compatibility.

It is a good practice not to rely on _prefix. A module should not make assumptions about its location in the configuration tree. For example, the root of a NixOS configuration may have a non-empty prefix, for example when it is a specialisation, or when it is part of a larger, multi-host configuration, such as a NixOS test. Instead of depending on _prefix use explicit options, whose default definitions can be provided by the module that imports them.

Standard environment

The Standard Environment

The standard build environment in the Nix Packages collection provides an environment for building Unix packages that does a lot of common build tasks automatically. In fact, for Unix packages that use the standard ./configure; make; make install build interface, you don’t need to write a build script at all; the standard environment does everything automatically. If stdenv doesn’t do what you need automatically, you can easily customise or override the various build phases.

Using stdenv

To build a package with the standard environment, you use the function stdenv.mkDerivation, instead of the primitive built-in function derivation, e.g.

stdenv.mkDerivation {
  name = "libfoo-1.2.3";
  src = fetchurl {
    url = "http://example.org/libfoo-1.2.3.tar.bz2";
    hash = "sha256-tWxU/LANbQE32my+9AXyt3nCT7NBVfJ45CX757EMT3Q=";
  };
}

(stdenv needs to be in scope, so if you write this in a separate Nix expression from pkgs/all-packages.nix, you need to pass it as a function argument.) Specifying a name and a src is the absolute minimum Nix requires. For convenience, you can also use pname and version attributes and mkDerivation will automatically set name to "${pname}-${version}" by default. Since RFC 0035, this is preferred for packages in Nixpkgs, as it allows us to reuse the version easily:

stdenv.mkDerivation (finalAttrs: {
  pname = "libfoo";
  version = "1.2.3";
  src = fetchurl {
    url = "http://example.org/libfoo-source-${finalAttrs.version}.tar.bz2";
    hash = "sha256-tWxU/LANbQE32my+9AXyt3nCT7NBVfJ45CX757EMT3Q=";
  };
})

Many packages have dependencies that are not provided in the standard environment. It’s usually sufficient to specify those dependencies in the buildInputs attribute:

stdenv.mkDerivation {
  pname = "libfoo";
  version = "1.2.3";
  # ...
  buildInputs = [
    libbar
    perl
    ncurses
  ];
}

This attribute ensures that the bin subdirectories of these packages appear in the PATH environment variable during the build, that their include subdirectories are searched by the C compiler, and so on. (See the section called “Package setup hooks” for details.)

Often it is necessary to override or modify some aspect of the build. To make this easier, the standard environment breaks the package build into a number of phases, all of which can be overridden or modified individually: unpacking the sources, applying patches, configuring, building, and installing. (There are some others; see the section called “Phases”.) For instance, a package that doesn’t supply a makefile but instead has to be compiled “manually” could be handled like this:

stdenv.mkDerivation {
  pname = "fnord";
  version = "4.5";

  # ...

  buildPhase = ''
    runHook preBuild

    gcc foo.c -o foo

    runHook postBuild
  '';

  installPhase = ''
    runHook preInstall

    mkdir -p $out/bin
    cp foo $out/bin

    runHook postInstall
  '';
}

(Note the use of ''-style string literals, which are very convenient for large multi-line script fragments because they don’t need escaping of " and \, and because indentation is intelligently removed.)

There are many other attributes to customise the build. These are listed in the section called “Attributes”.

While the standard environment provides a generic builder, you can still supply your own build script:

stdenv.mkDerivation {
  pname = "libfoo";
  version = "1.2.3";
  # ...
  builder = ./builder.sh;
}

where stdenv sets up the environment automatically (e.g. by resetting PATH and populating it from build inputs). If you want, you can use stdenv’s generic builder:

buildPhase() {
  echo "... this is my custom build phase ..."
  gcc foo.c -o foo
}

installPhase() {
  mkdir -p $out/bin
  cp foo $out/bin
}

genericBuild

Building a stdenv package in nix-shell

To build a stdenv package in a nix-shell, enter a shell, find the phases you wish to build, then invoke genericBuild manually:

Go to an empty directory, invoke nix-shell with the desired package, and from inside the shell, set the output variables to a writable directory:

cd "$(mktemp -d)"
nix-shell '<nixpkgs>' -A some_package
export out=$(pwd)/out

Next, invoke the desired parts of the build. First, run the phases that generate a working copy of the sources, which will change directory to the sources for you:

phases="${prePhases[*]:-} unpackPhase patchPhase" genericBuild

Then, run more phases up until the failure is reached. If the failure is in the build or check phase, the following phases would be required:

phases="${preConfigurePhases[*]:-} configurePhase ${preBuildPhases[*]:-} buildPhase checkPhase" genericBuild

Use this command to run all install phases:

phases="${preInstallPhases[*]:-} installPhase ${preFixupPhases[*]:-} fixupPhase installCheckPhase" genericBuild

Single phase can be re-run as many times as necessary to examine the failure like so:

phases="buildPhase" genericBuild

To modify a phase, first print it with

echo "$buildPhase"

Or, if that is empty, for instance, if it is using a function:

type buildPhase

then change it in a text editor, and paste it back to the terminal.

Note

This method may have some inconsistencies in environment variables and behaviour compared to a normal build within the Nix build sandbox. The following is a non-exhaustive list of such differences:

  • TMP, TMPDIR, and similar variables likely point to non-empty directories that the build might conflict with files in.

  • Output store paths are not writable, so the variables for outputs need to be overridden to writable paths.

  • Other environment variables may be inconsistent with a nix-build either due to nix-shell’s initialization script or due to the use of nix-shell without the --pure option.

If the build fails differently inside the shell than in the sandbox, consider using breakpointHook and invoking nix-build instead. The --keep-failed option for nix-build may also be useful to examine the build directory of a failed build.

Tools provided by stdenv

The standard environment provides the following packages:

  • The GNU C Compiler, configured with C and C++ support.

  • GNU coreutils (contains a few dozen standard Unix commands).

  • GNU findutils (contains find).

  • GNU diffutils (contains diff, cmp).

  • GNU sed.

  • GNU grep.

  • GNU awk.

  • GNU tar.

  • gzip, bzip2 and xz.

  • GNU Make.

  • Bash. This is the shell used for all builders in the Nix Packages collection. Not using /bin/sh removes a large source of portability problems.

  • The patch command.

On Linux, stdenv also includes the patchelf utility.

Specifying dependencies

Build systems often require more dependencies than just what stdenv provides. This section describes attributes accepted by stdenv.mkDerivation that can be used to make these dependencies available to the build system.

Overview

A full reference of the different kinds of dependencies is provided in the section called “Reference”, but here is an overview of the most common ones. It should cover most use cases.

Add dependencies to nativeBuildInputs if they are executed during the build:

  • those which are needed on $PATH during the build, for example cmake and pkg-config

  • setup hooks, for example makeWrapper

  • interpreters needed by patchShebangs for build scripts (with the --build flag), which can be the case for e.g. perl

Add dependencies to buildInputs if they will end up copied or linked into the final output or otherwise used at runtime:

  • libraries used by compilers, for example zlib,

  • interpreters needed by patchShebangs for scripts which are installed, which can be the case for e.g. perl

Note

These criteria are independent.

For example, software using Wayland usually needs the wayland library at runtime, so wayland should be added to buildInputs. But it also executes the wayland-scanner program as part of the build to generate code, so wayland should also be added to nativeBuildInputs.

Dependencies needed only to run tests are similarly classified between native (executed during build) and non-native (executed at runtime):

  • nativeCheckInputs for test tools needed on $PATH (such as ctest) and setup hooks (for example pytestCheckHook)

  • checkInputs for libraries linked into test executables (for example the qcheck OCaml package)

These dependencies are only injected when doCheck is set to true.

Example

Consider for example this simplified derivation for solo5, a sandboxing tool:

stdenv.mkDerivation (finalAttrs: {
  pname = "solo5";
  version = "0.7.5";

  src = fetchurl {
    url = "https://github.com/Solo5/solo5/releases/download/v${finalAttrs.version}/solo5-v${finalAttrs.version}.tar.gz";
    hash = "sha256-viwrS9lnaU8sTGuzK/+L/PlMM/xRRtgVuK5pixVeDEw=";
  };

  nativeBuildInputs = [
    makeWrapper
    pkg-config
  ];

  buildInputs = [ libseccomp ];

  postInstall = ''
    substituteInPlace $out/bin/solo5-virtio-mkimage \
      --replace-fail "/usr/lib/syslinux" "${syslinux}/share/syslinux" \
      --replace-fail "/usr/share/syslinux" "${syslinux}/share/syslinux" \
      --replace-fail "cp " "cp --no-preserve=mode "

    wrapProgram $out/bin/solo5-virtio-mkimage \
      --prefix PATH : ${
        lib.makeBinPath [
          dosfstools
          mtools
          parted
          syslinux
        ]
      }
  '';

  doCheck = true;
  nativeCheckInputs = [
    util-linux
    qemu
  ];
  # `checkPhase` elided
})
  • makeWrapper is a setup hook, i.e., a shell script sourced by the generic builder of stdenv. It is thus executed during the build and must be added to nativeBuildInputs.

  • pkg-config is a build tool which the configure script of solo5 expects to be on $PATH during the build: therefore, it must be added to nativeBuildInputs.

  • libseccomp is a library linked into $out/bin/solo5-elftool. As it is used at runtime, it must be added to buildInputs.

  • Tests need qemu and getopt (from util-linux) on $PATH, these must be added to nativeCheckInputs.

  • Some dependencies are injected directly in the shell code of phases: syslinux, dosfstools, mtools, and parted. In this specific case, they will end up in the output of the derivation ($out here). As Nix marks dependencies whose absolute path is present in the output as runtime dependencies, adding them to buildInputs is not required.

For more complex cases, like libraries linked into an executable which is then executed as part of the build system, see the section called “Reference”.

Reference

As described in the Nix manual, almost any *.drv store path in a derivation’s attribute set will induce a dependency on that derivation. mkDerivation, however, takes a few attributes intended to include all the dependencies of a package. This is done both for structure and consistency, but also so that certain other setup can take place. For example, certain dependencies need their bin directories added to the PATH. That is built-in, but other setup is done via a pluggable mechanism that works in conjunction with these dependency attributes. See the section called “Package setup hooks” for details.

Dependencies can be broken down along these axes: their host and target platforms relative to the new derivation’s. The platform distinctions are motivated by cross compilation; see Cross-compilation for exactly what each platform means. [1] But even if one is not cross compiling, the platforms imply whether a dependency is needed at run-time or build-time.

The extension of PATH with dependencies, alluded to above, proceeds according to the relative platforms alone. The process is carried out only for dependencies whose host platform matches the new derivation’s build platform i.e. dependencies which run on the platform where the new derivation will be built. [2] For each dependency <dep> of those dependencies, dep/bin, if present, is added to the PATH environment variable.

Dependency propagation

Propagated dependencies are made available to all downstream dependencies. This is particularly useful for interpreted languages, where all transitive dependencies have to be present in the same environment. Therefore it is used for the Python infrastructure in Nixpkgs.

Note

Propagated dependencies should be used with care, because they obscure the actual build inputs of dependent derivations and cause side effects through setup hooks. This can lead to conflicting dependencies that cannot easily be resolved.

Example 300. A propagated dependency
with import <nixpkgs> { };
let
  bar = stdenv.mkDerivation {
    name = "bar";
    dontUnpack = true;
    # `hello` is also made available to dependents, such as `foo`
    propagatedBuildInputs = [ hello ];
    postInstall = "mkdir $out";
  };
  foo = stdenv.mkDerivation {
    name = "foo";
    dontUnpack = true;
    # `bar` is a direct dependency, which implicitly includes the propagated `hello`
    buildInputs = [ bar ];
    # The `hello` binary is available!
    postInstall = "hello > $out";
  };
in
foo

Dependency propagation takes cross compilation into account, meaning that dependencies that cross platform boundaries are properly adjusted.

To determine the exact rules for dependency propagation, we start by assigning to each dependency a couple of ternary numbers (-1 for build, 0 for host, and 1 for target) representing its dependency type, which captures how its host and target platforms are each “offset” from the depending derivation’s host and target platforms. The following table summarize the different combinations that can be obtained:

Dependency typeattribute nameoffsettypical purpose
build → builddepsBuildBuild-1, -1compilers for build helpers
build → hostnativeBuildInputs-1, 0build tools, compilers, setup hooks
build → targetdepsBuildTarget-1, 1compilers to build stdlibs to run on target
host → hostdepsHostHost0, 0compilers to build C code at runtime (rare)
host → targetbuildInputs0, 1libraries
target → targetdepsTargetTarget1, 1stdlibs to run on target

Algorithmically, we traverse propagated inputs, accumulating every propagated dependency’s propagated dependencies and adjusting them to account for the “shift in perspective” described by the current dependency’s platform offsets. This results in a sort of transitive closure of the dependency relation, with the offsets being approximately summed when two dependency links are combined. We also prune transitive dependencies whose combined offsets go out-of-bounds, which can be viewed as a filter over that transitive closure removing dependencies that are blatantly absurd.

We can define the process precisely with Natural Deduction using the inference rules below. This probably seems a bit obtuse, but so is the bash code that actually implements it! [3] They’re confusing in very different ways so… hopefully if something doesn’t make sense in one presentation, it will in the other!

Definitions:

dep(h_offset, t_offset, X, Y)

Package X has a direct dependency on Y in a position with host offset h_offset and target offset t_offset.

For example, nativeBuildInputs = [ Y ] means dep(-1, 0, X, Y).

propagated-dep(h_offset, t_offset, X, Y)

Package X has a propagated dependency on Y in a position with host offset h_offset and target offset t_offset.

For example, depsBuildTargetPropagated = [ Y ] means propagated-dep(-1, 1, X, Y).

mapOffset(h, t, i) = offs

In a package X with a dependency on Y in a position with host offset h and target offset t, Y’s transitive dependency Z in a position with offset i is mapped to offset offs in X.

Example 301. Truth table of mapOffset(h, t, i)

x means that the dependency was discarded because h + i ∉ {-1, 0, 1}.

  h |   t  || i=-1 |  i=0 |  i=1
----|------||------|------|-----
 -1 |  -1  ||   x  |  -1  |  -1
 -1 |   0  ||   x  |  -1  |   0
 -1 |   1  ||   x  |  -1  |   1
  0 |   0  ||  -1  |   0  |   0
  0 |   1  ||  -1  |   0  |   1
  1 |   1  ||   0  |   1  |   x

let mapOffset(h, t, i) = i + (if i <= 0 then h else t - 1)

propagated-dep(h0, t0, A, B)
propagated-dep(h1, t1, B, C)
h0 + h1 in {-1, 0, 1}
h0 + t1 in {-1, 0, 1}
-------------------------------------- Transitive property
propagated-dep(mapOffset(h0, t0, h1),
               mapOffset(h0, t0, t1),
               A, C)
let mapOffset(h, t, i) = i + (if i <= 0 then h else t - 1)

dep(h0, t0, A, B)
propagated-dep(h1, t1, B, C)
h0 + h1 in {-1, 0, 1}
h0 + t1 in {-1, 0, 1}
----------------------------- Take immediate dependencies' propagated dependencies
propagated-dep(mapOffset(h0, t0, h1),
               mapOffset(h0, t0, t1),
               A, C)
propagated-dep(h, t, A, B)
----------------------------- Propagated dependencies count as dependencies
dep(h, t, A, B)

Some explanation of this monstrosity is in order. In the common case of nativeBuildInputs or buildInputs, the target offset of a dependency is one greater than the host offset: t = h + 1. That means that:

let f(h, t, i) = i + (if i <= 0 then h else t - 1)
let f(h, h + 1, i) = i + (if i <= 0 then h else (h + 1) - 1)
let f(h, h + 1, i) = i + (if i <= 0 then h else h)
let f(h, h + 1, i) = i + h

This is where “sum-like” comes in from above: We can just sum all of the host offsets to get the host offset of the transitive dependency. The target offset is the transitive dependency is the host offset + 1, just as it was with the dependencies composed to make this transitive one; it can be ignored as it doesn’t add any new information.

Because of the bounds checks, the uncommon cases are h = t (depsBuildBuild, etc) and h + 2 = t (depsBuildTarget).

In the former case, the motivation for mapOffset is that since its host and target platforms are the same, no transitive dependency of it should be able to “discover” an offset greater than its reduced target offsets. mapOffset effectively “squashes” all its transitive dependencies’ offsets so that none will ever be greater than the target offset of the original h = t package.

In the other case, h + 1 (0) is skipped over between the host (-1) and target (1) offsets. Instead of squashing the offsets, we need to “rip” them apart so no transitive dependency’s offset is 0.

Overall, the unifying theme here is that propagation shouldn’t be introducing transitive dependencies involving platforms the depending package is unaware of. [One can imagine the depending package asking for dependencies with the platforms it knows about; other platforms it doesn’t know how to ask for. The platform description in that scenario is a kind of unforgeable capability.] The offset bounds checking and definition of mapOffset together ensure that this is the case. Discovering a new offset is discovering a new platform, and since those platforms weren’t in the derivation “spec” of the needing package, they cannot be relevant. From a capability perspective, we can imagine that the host and target platforms of a package are the capabilities a package requires, and the depending package must provide the capability to the dependency.

Variables specifying dependencies

depsBuildBuild

A list of dependencies whose host and target platforms are the new derivation’s build platform. These are programs and libraries used at build time that produce programs and libraries also used at build time. If the dependency doesn’t care about the target platform (i.e. isn’t a compiler or similar tool), put it in nativeBuildInputs instead. The most common use of this buildPackages.stdenv.cc (the compiler for buildPackages, which means that it’s from the package set buildPackages.buildPackages = pkgsBuildBuild), the default C compiler for this role. That example crops up more than one might think in old commonly used C libraries.

Since these packages are able to be run at build-time, they are always added to the PATH, as described above. But since these packages are only guaranteed to be able to run then, they shouldn’t persist as run-time dependencies. This isn’t currently enforced, but could be in the future.

nativeBuildInputs

A list of dependencies whose host platform is the new derivation’s build platform, and target platform is the new derivation’s host platform. These are programs and libraries used at build-time that, if they are a compiler or similar tool, produce code to run at run-time—i.e. tools used to build the new derivation. If the dependency doesn’t care about the target platform (i.e. isn’t a compiler or similar tool), put it here, rather than in depsBuildBuild or depsBuildTarget. This could be called depsBuildHost, but nativeBuildInputs is used for historical continuity.

Since these packages are able to be run at build-time, they are added to the PATH, as described above. But since these packages are only guaranteed to be able to run then, they shouldn’t persist as run-time dependencies. This isn’t currently enforced, but could be in the future.

depsBuildTarget

A list of dependencies whose host platform is the new derivation’s build platform, and target platform is the new derivation’s target platform. These are programs used at build time that produce code to run with code produced by the depending package. Most commonly, these are tools used to build the runtime or standard library that the currently-being-built compiler will inject into any code it compiles. In many cases, the currently-being-built-compiler is itself employed for that task, but when that compiler won’t run (i.e. its build and host platform differ) this is not possible. Other times, the compiler relies on some other tool, like binutils, that is always built separately so that the dependency is unconditional.

This is a somewhat confusing concept to wrap one’s head around, and for good reason. As the only dependency type where the platform offsets, -1 and 1, are not adjacent integers, it requires thinking of a bootstrapping stage two away from the current one. It and its use-case go hand in hand and are both considered poor form: try to not need this sort of dependency, and try to avoid building standard libraries and runtimes in the same derivation as the compiler produces code using them. Instead strive to build those like a normal library, using the newly-built compiler just as a normal library would. In short, do not use this attribute unless you are packaging a compiler and are sure it is needed.

Since these packages are able to run at build time, they are added to the PATH, as described above. But since these packages are only guaranteed to be able to run then, they shouldn’t persist as run-time dependencies. This isn’t currently enforced, but could be in the future.

depsHostHost

A list of dependencies whose host and target platforms match the new derivation’s host platform. In practice, this would usually be tools used by compilers for macros or a metaprogramming system, or libraries used by the macros or metaprogramming code itself. It’s always preferable to use a depsBuildBuild dependency in the derivation being built over a depsHostHost on the tool doing the building for this purpose.

buildInputs

A list of dependencies whose host platform and target platform match the new derivation’s. This would be called depsHostTarget but for historical continuity. If the dependency doesn’t care about the target platform (i.e. isn’t a compiler or similar tool), put it here, rather than in depsBuildBuild.

These are often programs and libraries used by the new derivation at run-time, but that isn’t always the case. For example, the machine code in a statically-linked library is only used at run-time, but the derivation containing the library is only needed at build-time. Even in the dynamic case, the library may also be needed at build-time to appease the linker.

depsTargetTarget

A list of dependencies whose host platform matches the new derivation’s target platform. These are packages that run on the target platform, e.g. the standard library or run-time deps of standard library that a compiler insists on knowing about. It’s poor form in almost all cases for a package to depend on another from a future stage [future stage corresponding to positive offset]. Do not use this attribute unless you are packaging a compiler and are sure it is needed.

depsBuildBuildPropagated

The propagated equivalent of depsBuildBuild. This perhaps never ought to be used, but it is included for consistency [see below for the others].

propagatedNativeBuildInputs

The propagated equivalent of nativeBuildInputs. This would be called depsBuildHostPropagated but for historical continuity. For example, if package Y has propagatedNativeBuildInputs = [X], and package Z has buildInputs = [Y], then package Z will be built as if it included package X in its nativeBuildInputs. Note that if instead, package Z has nativeBuildInputs = [Y], then X will not be included at all.

depsBuildTargetPropagated

The propagated equivalent of depsBuildTarget. This is prefixed for the same reason of alerting potential users.

depsHostHostPropagated

The propagated equivalent of depsHostHost.

propagatedBuildInputs

The propagated equivalent of buildInputs. This would be called depsHostTargetPropagated but for historical continuity.

depsTargetTargetPropagated

The propagated equivalent of depsTargetTarget. This is prefixed for the same reason of alerting potential users.

strictDeps

When using native compilation, stdenv is lenient towards incorrect placement of a dependency into one of the dependency lists described above. That means a dependency needed at runtime often works, even if it is only present in nativeBuildInputs. Vice-versa, dependencies containing binaries that need to be executed during the build will work even if they are only listed in buildInputs.

While convenient for getting to a package quickly, this behavior can break cross-compilation. Adding strictDeps = true as a parameter to mkDerivation or any of its language specific wrappers disables this behavior.

The specialized build* functions for dlang, emacs, go, nim, ocaml, python, and rust enable this option by default.

Attributes

Variables affecting stdenv initialisation

NIX_DEBUG

A number between 0 and 7 indicating how much information to log. If set to 1 or higher, stdenv will print moderate debugging information during the build. In particular, the gcc and ld wrapper scripts will print out the complete command line passed to the wrapped tools. If set to 6 or higher, the stdenv setup script will be run with set -x tracing. If set to 7 or higher, the gcc and ld wrapper scripts will also be run with set -x tracing.

Attributes affecting build properties

enableParallelBuilding

If set to true, stdenv will pass specific flags to make and other build tools to enable parallel building with up to build-cores workers.

Unless set to false, some build systems with good support for parallel building including cmake, meson, and qmake will set it to true.

__structuredAttrs

__structuredAttrs defines how derivation attributes are passed to the builder.

If enabled, a shell script and a JSON representation of the derivation attributes are created. The environment variables NIX_ATTRS_SH_FILE and NIX_ATTRS_JSON_FILE point to the exact location of these files.

Attributes intended to be exported as environment variables must be defined in the env attribute. Attributes that are local to the buildscript should be defined outside of env, to benefit from structured shell variables.

Important

__structuredAttrs is a complete replacement for the way attributes are handled currently, and is the preferred default.

passAsFile is disabled when __structuredAttrs is enabled, since NIX_ATTRS_JSON_FILE can be read from instead.

All new top level packages must enable __structuredAttrs.

See the upstream nix documentation for more detail:

Fixed-point arguments of mkDerivation

If you pass a function to mkDerivation, it will call the function with an argument that represents the final state of the package: the return value of the function itself, with any overrides applied, as the function is reinvoked by any overrideAttrs calls. For example:

mkDerivation (finalAttrs: {
  pname = "hello";
  withFeature = true;
  configureFlags = lib.optionals finalAttrs.withFeature [ "--with-feature" ];
})

Note that this does not use the rec keyword to reuse withFeature in configureFlags. The rec keyword works at the syntax level and is unaware of overriding.

Instead, the definition references finalAttrs, allowing users to change withFeature consistently with overrideAttrs.

finalAttrs also contains the attribute finalPackage, which includes the output paths, etc.

Let’s look at a more elaborate example to understand the differences between various bindings:

# `pkg` is the _original_ definition (for illustration purposes)
let
  pkg = mkDerivation (finalAttrs: {
    # ...

    # An example attribute
    packages = [ ];

    # `passthru.tests` is a commonly defined attribute.
    passthru.tests.simple = f finalAttrs.finalPackage;

    # An example of an attribute containing a function
    passthru.appendPackages =
      packages':
      finalAttrs.finalPackage.overrideAttrs (newSelf: super: { packages = super.packages ++ packages'; });

    # For illustration purposes; referenced as
    # `(pkg.overrideAttrs(x)).finalAttrs` etc in the text below.
    passthru.finalAttrs = finalAttrs;
    passthru.original = pkg;
  });
in
pkg

Unlike the pkg binding in the above example, the finalAttrs parameter always references the final attributes. For instance (pkg.overrideAttrs(x)).finalAttrs.finalPackage is identical to pkg.overrideAttrs(x), whereas (pkg.overrideAttrs(x)).original is the same as the original pkg.

See also the section about passthru.tests.

Phases

stdenv.mkDerivation sets the Nix derivation’s builder to a script that loads the stdenv setup.sh bash library and calls genericBuild. Most packaging functions rely on this default builder.

This generic command either invokes a script at buildCommandPath, or a buildCommand, or a number of phases. Package builds are split into phases to make it easier to override specific parts of the build (e.g., unpacking the sources or installing the binaries).

Each phase can be overridden in its entirety either by setting the environment variable namePhase to a string containing some shell commands to be executed, or by redefining the shell function namePhase. The former is convenient to override a phase from the derivation, while the latter is convenient from a build script. However, typically one only wants to add some commands to a phase, e.g. by defining postInstall or preFixup, as skipping some of the default actions may have unexpected consequences. The default script for each phase is defined in the file pkgs/stdenv/generic/setup.sh.

When overriding a phase, for example installPhase, it is important to start with runHook preInstall and end it with runHook postInstall, otherwise preInstall and postInstall will not be run. Even if you don’t use them directly, it is good practice to do so anyways for downstream users who would want to add a postInstall by overriding your derivation.

While inside an interactive nix-shell, if you wanted to run all phases in the order they would be run in an actual build, you can invoke genericBuild yourself.

Controlling phases

There are a number of variables that control what phases are executed and in what order:

Variables affecting phase control

phases

Specifies the phases. You can change the order in which phases are executed, or add new phases, by setting this variable. If it’s not set, the default value is used, which is $prePhases unpackPhase patchPhase $preConfigurePhases configurePhase $preBuildPhases buildPhase checkPhase $preInstallPhases installPhase fixupPhase installCheckPhase $preDistPhases distPhase $postPhases.

The elements of phases must not contain spaces. If phases is specified as a Nix Language attribute, it should be specified as lists instead of strings. The same rules apply to the *Phases variables.

It is discouraged to set this variable, as it is easy to miss some important functionality hidden in some of the less obviously needed phases (like fixupPhase which patches the shebang of scripts). Usually, if you just want to add a few phases, it’s more convenient to set one of the *Phases variables below.

prePhases

Additional phases executed before any of the default phases.

preConfigurePhases

Additional phases executed just before the configure phase.

preBuildPhases

Additional phases executed just before the build phase.

preInstallPhases

Additional phases executed just before the install phase.

preFixupPhases

Additional phases executed just before the fixup phase.

preDistPhases

Additional phases executed just before the distribution phase.

postPhases

Additional phases executed after any of the default phases.

The unpack phase

The unpack phase is responsible for unpacking the source code of the package. The default implementation of unpackPhase unpacks the source files listed in the src environment variable to the current directory. It supports the following files by default:

Tar files

These can optionally be compressed using gzip (.tar.gz, .tgz or .tar.Z), bzip2 (.tar.bz2, .tbz2 or .tbz) or xz (.tar.xz, .tar.lzma or .txz).

Zip files

Zip files are unpacked using unzip. However, unzip is not in the standard environment, so you should add it to nativeBuildInputs yourself.

Directories in the Nix store

These are copied to the current directory. The hash part of the file name is stripped, e.g. /nix/store/1wydxgby13cz...-my-sources would be copied to my-sources.

Additional file types can be supported by setting the unpackCmd variable (see below).

Variables controlling the unpack phase

srcs / src

The list of source files or directories to be unpacked or copied. One of these must be set. Note that if you use srcs, you should also set sourceRoot or setSourceRoot.

These should ideally actually be sources and licensed under a FLOSS license. If you have to use a binary upstream release or package non-free software, make sure you correctly mark your derivation as such in the sourceProvenance and license fields of the meta section.

sourceRoot

After unpacking all of src and srcs, if neither of sourceRoot and setSourceRoot are set, unpackPhase of the generic builder checks that the unpacking produced a single directory and moves the current working directory into it.

If unpackPhase produces multiple source directories, you should set sourceRoot to the name of the intended directory. You can also set sourceRoot = "."; if you want to control it yourself in a later phase.

For example, if you want your build to start in a sub-directory inside your sources, and you are using fetchzip-derived src (like fetchFromGitHub or similar), you need to set sourceRoot = "${src.name}/my-sub-directory".

setSourceRoot

Alternatively to setting sourceRoot, you can set setSourceRoot to a shell command to be evaluated by the unpack phase after the sources have been unpacked. This command must set sourceRoot.

For example, if you are using fetchurl on an archive file that gets unpacked into a single directory the name of which changes between package versions, and you want your build to start in its sub-directory, you need to set setSourceRoot = "sourceRoot=$(echo */my-sub-directory)";, or in the case of multiple sources, you could use something more specific, like setSourceRoot = "sourceRoot=$(echo ${pname}-*/my-sub-directory)";.

preUnpack

Hook executed at the start of the unpack phase.

postUnpack

Hook executed at the end of the unpack phase.

dontUnpack

Set to true to skip the unpack phase.

dontMakeSourcesWritable

If set to 1, the unpacked sources are not made writable. By default, they are made writable to prevent problems with read-only sources. For example, copied store directories would be read-only without this.

unpackCmd

The unpack phase evaluates the string $unpackCmd for any unrecognised file. The path to the current source file is contained in the curSrc variable.

The patch phase

The patch phase applies the list of patches defined in the patches variable.

Variables controlling the patch phase

dontPatch

Set to true to skip the patch phase.

patches

The list of patches. They must be in the format accepted by the patch command, and may optionally be compressed using gzip (.gz), bzip2 (.bz2) or xz (.xz).

patchFlags

Flags to be passed to patch. If not set, the argument -p1 is used, which causes the leading directory component to be stripped from the file names in each patch.

prePatch

Hook executed at the start of the patch phase.

postPatch

Hook executed at the end of the patch phase.

The configure phase

The configure phase prepares the source tree for building. The default configurePhase runs ./configure (typically an Autoconf-generated script) if it exists.

Variables controlling the configure phase

configureScript

The name of the configure script. It defaults to ./configure if it exists; otherwise, the configure phase is skipped. This can actually be a command (like perl ./Configure.pl).

configureFlags

A list of strings passed as additional arguments to the configure script.

dontConfigure

Set to true to skip the configure phase.

configureFlagsArray

A shell array containing additional arguments passed to the configure script. You must use this instead of configureFlags if the arguments contain spaces.

dontAddPrefix

By default, ./configure is passed the concatenation of prefixKey and prefix on the command line. Disable this by setting dontAddPrefix to true.

prefix

The prefix under which the package must be installed, passed via the --prefix option to the configure script. It defaults to $out.

prefixKey

The key to use when specifying the installation prefix. By default, this is set to --prefix= as that is used by the majority of packages. Other packages may need --prefix (with a trailing space) or PREFIX=.

dontAddStaticConfigureFlags

By default, when building statically, stdenv will try to add build system appropriate configure flags to try to enable static builds.

If this is undesirable, set this variable to true.

dontAddDisableDepTrack

By default, the flag --disable-dependency-tracking is added to the configure flags to speed up Automake-based builds. If this is undesirable, set this variable to true.

dontFixLibtool

By default, the configure phase applies some special hackery to all files called ltmain.sh before running the configure script in order to improve the purity of Libtool-based packages [4] . If this is undesirable, set this variable to true.

dontDisableStatic

By default, when the configure script has --enable-static, the option --disable-static is added to the configure flags.

If this is undesirable, set this variable to true. It is automatically set to true when building statically, for example through pkgsStatic.

configurePlatforms

By default, when cross compiling, the configure script has --build=... and --host=... passed. Packages can instead pass [ "build" "host" "target" ] or a subset to control exactly which platform flags are passed. Compilers and other tools can use this to also pass the target platform. [5]

preConfigure

Hook executed at the start of the configure phase.

postConfigure

Hook executed at the end of the configure phase.

The build phase

The build phase is responsible for actually building the package (e.g. compiling it). The default buildPhase calls make if a file named Makefile, makefile or GNUmakefile exists in the current directory (or the makefile is explicitly set); otherwise it does nothing.

Variables controlling the build phase

dontBuild

Set to true to skip the build phase.

makefile

The file name of the Makefile.

makeFlags

A list of strings passed as additional flags to make. These flags are also used by the default install and check phase. For setting make flags specific to the build phase, use buildFlags (see below).

{ makeFlags = [ "PREFIX=$(out)" ]; }

Note

The flags are quoted in bash, but environment variables can be specified by using the make syntax.

makeFlagsArray

A shell array containing additional arguments passed to make. You must use this instead of makeFlags if the arguments contain spaces, e.g.

{
  preBuild = ''
    makeFlagsArray+=(CFLAGS="-O0 -g" LDFLAGS="-lfoo -lbar")
  '';
}

Note that shell arrays cannot be passed through environment variables, so you cannot set makeFlagsArray in a derivation attribute (because those are passed through environment variables): you have to define them in shell code.

buildFlags / buildFlagsArray

A list of strings passed as additional flags to make. Like makeFlags and makeFlagsArray, but only used by the build phase. Any build targets should be specified as part of the buildFlags.

preBuild

Hook executed at the start of the build phase.

postBuild

Hook executed at the end of the build phase.

You can set flags for make through the makeFlags variable.

Before and after running make, the hooks preBuild and postBuild are called, respectively.

The check phase

The check phase checks whether the package was built correctly by running its test suite. The default checkPhase calls make $checkTarget, but only if the doCheck variable is enabled.

It is highly recommended, for packages’ sources that are not distributed with any tests, to at least use versionCheckHook to test that the resulting executable is basically functional.

Variables controlling the check phase

doCheck

Controls whether the check phase is executed. By default it is skipped, but if doCheck is set to true, the check phase is usually executed. Thus you should set

{ doCheck = true; }

in the derivation to enable checks. The exception is cross compilation. Cross compiled builds never run tests, no matter how doCheck is set, as the newly-built program won’t run on the platform used to build it.

makeFlags / makeFlagsArray / makefile

See the build phase for details.

checkTarget

The make target that runs the tests. If unset, use check if it exists, otherwise test; if neither is found, do nothing.

checkFlags / checkFlagsArray

A list of strings passed as additional flags to make. Like makeFlags and makeFlagsArray, but only used by the check phase. Unlike with buildFlags, the checkTarget is automatically added to the make invocation in addition to any checkFlags specified.

checkInputs

A list of host dependencies used by the phase, usually libraries linked into executables built during tests. This gets included in buildInputs when doCheck is set.

nativeCheckInputs

A list of native dependencies used by the phase, notably tools needed on $PATH. This gets included in nativeBuildInputs when doCheck is set.

preCheck

Hook executed at the start of the check phase.

postCheck

Hook executed at the end of the check phase.

The install phase

The install phase is responsible for installing the package in the Nix store under out. The default installPhase creates the directory $out and calls make install.

Variables controlling the install phase

dontInstall

Set to true to skip the install phase.

makeFlags / makeFlagsArray / makefile

See the build phase for details.

installTargets

The make targets that perform the installation. Defaults to install. Example:

{ installTargets = "install-bin install-doc"; }
installFlags / installFlagsArray

A list of strings passed as additional flags to make. Like makeFlags and makeFlagsArray, but only used by the install phase. Unlike with buildFlags, the installTargets are automatically added to the make invocation in addition to any installFlags specified.

preInstall

Hook executed at the start of the install phase.

postInstall

Hook executed at the end of the install phase.

The fixup phase

The fixup phase performs (Nix-specific) post-processing actions on the files installed under $out by the install phase. The default fixupPhase does the following:

  • It moves the man/, doc/ and info/ subdirectories of $out to share/.

  • It strips libraries and executables of debug information.

  • On Linux, it applies the patchelf command to ELF executables and libraries to remove unused directories from the RPATH in order to prevent unnecessary runtime dependencies.

  • It rewrites the interpreter paths of shell scripts to paths found in PATH. E.g., /usr/bin/perl will be rewritten to /nix/store/some-perl/bin/perl found in PATH. See the section called “patch-shebangs.sh for details.

Variables controlling the fixup phase

dontFixup

Set to true to skip the fixup phase.

dontStrip

If set, libraries and executables are not stripped. By default, they are.

dontStripHost

Like dontStrip, but only affects the strip command targeting the package’s host platform. Useful when supporting cross compilation, but otherwise feel free to ignore.

dontStripTarget

Like dontStrip, but only affects the strip command targeting the packages’ target platform. Useful when supporting cross compilation, but otherwise feel free to ignore.

dontMoveSbin

If set, files in $out/sbin are not moved to $out/bin. By default, they are.

stripAllList

List of directories to search for libraries and executables from which all symbols should be stripped. By default, it’s empty. Stripping all symbols is risky, since it may remove not just debug symbols but also ELF information necessary for normal execution.

stripAllListTarget

Like stripAllList, but only applies to packages’ target platform. By default, it’s empty. Useful when supporting cross compilation.

stripAllFlags

Flags passed to the strip command applied to the files in the directories listed in stripAllList. Defaults to -s -p (i.e. --strip-all --preserve-dates).

stripDebugList

List of directories to search for libraries and executables from which only debugging-related symbols should be stripped. It defaults to lib lib32 lib64 libexec bin sbin.

stripDebugListTarget

Like stripDebugList, but only applies to packages’ target platform. By default, it’s empty. Useful when supporting cross compilation.

stripDebugFlags

Flags passed to the strip command applied to the files in the directories listed in stripDebugList. Defaults to -S -p (i.e. --strip-debug --preserve-dates).

stripExclude

A list of filenames or path patterns to avoid stripping. A file is excluded if its name or path (from the derivation root) matches.

This example prevents all *.rlib files from being stripped:

stdenv.mkDerivation {
  # ...
  stripExclude = [ "*.rlib" ];
}

This example prevents files within certain paths from being stripped:

stdenv.mkDerivation {
  # ...
  stripExclude = [ "lib/modules/*/build/*" ];
}
dontPatchELF

If set, the patchelf command is not used to remove unnecessary RPATH entries. Only applies to Linux.

dontPatchShebangs

If set, scripts starting with #! do not have their interpreter paths rewritten to paths in the Nix store. See the section called “patch-shebangs.sh on how patching shebangs works.

dontPruneLibtoolFiles

If set, libtool .la files associated with shared libraries won’t have their dependency_libs field cleared.

forceShare

The list of directories that must be moved from $out to $out/share. Defaults to man doc info.

setupHook

A package can export a setup hook by setting this variable. The setup hook, if defined, is copied to $out/nix-support/setup-hook. Environment variables are then substituted in it using substituteAll.

preFixup

Hook executed at the start of the fixup phase.

postFixup

Hook executed at the end of the fixup phase.

separateDebugInfo

If set to true, the standard environment will enable debug information in C/C++ builds. After installation, the debug information will be separated from the executables and stored in the output named debug. (This output is enabled automatically; you don’t need to set the outputs attribute explicitly.) To be precise, the debug information is stored in debug/lib/debug/.build-id/XX/YYYY…, where <XXYYYY…> is the <build ID> of the binary — a SHA-1 hash of the contents of the binary. Debuggers like GDB use the build ID to look up the separated debug information.

Example 302. Enable debug symbols for use with GDB

To make GDB find debug information for the socat package and its dependencies, you can use the following shell.nix:

{
  pkgs ? import <nixpkgs> {
    config = { };
    overlays = [
      (final: prev: {
        ncurses = prev.ncurses.overrideAttrs { separateDebugInfo = true; };
        readline = prev.readline.overrideAttrs { separateDebugInfo = true; };
      })
    ];
  },
}:
pkgs.mkShell {
  NIX_DEBUG_INFO_DIRS = pkgs.lib.makeSearchPathOutput "debug" "lib/debug" [
    pkgs.glibc
    pkgs.ncurses
    pkgs.openssl
    pkgs.readline
  ];

  packages = [
    pkgs.gdb
    pkgs.socat
  ];

  shellHook = ''
    gdb socat
  '';
}

This setup works as follows:

  • Add overlays to the package set, since debug symbols are disabled for ncurses and readline by default.

  • Set the environment variable NIX_DEBUG_INFO_DIRS in the shell. Nixpkgs patches gdb to use this variable for looking up debug symbols. lib.makeSearchPathOutput constructs a colon-separated search path, pointing to the directories containing the debug symbols of the listed packages.

  • Run gdb on the socat binary on shell startup in the shellHook.


The installCheck phase

The installCheck phase checks whether the package was installed correctly by running its test suite against the installed directories. The default installCheck calls make installcheck.

It is often better to add tests that are not part of the source distribution to passthru.tests (see the section called “passthru.tests). This avoids adding overhead to every build and enables us to run them independently.

Variables controlling the installCheck phase

doInstallCheck

Controls whether the installCheck phase is executed. By default it is skipped, but if doInstallCheck is set to true, the installCheck phase is usually executed. Thus you should set

{ doInstallCheck = true; }

in the derivation to enable install checks. The exception is cross compilation. Cross compiled builds never run tests, no matter how doInstallCheck is set, as the newly-built program won’t run on the platform used to build it.

installCheckTarget

The make target that runs the install tests. Defaults to installcheck.

installCheckFlags / installCheckFlagsArray

A list of strings passed as additional flags to make. Like makeFlags and makeFlagsArray, but only used by the installCheck phase.

installCheckInputs

A list of host dependencies used by the phase, usually libraries linked into executables built during tests. This gets included in buildInputs when doInstallCheck is set.

nativeInstallCheckInputs

A list of native dependencies used by the phase, notably tools needed on $PATH. This gets included in nativeBuildInputs when doInstallCheck is set.

preInstallCheck

Hook executed at the start of the installCheck phase.

postInstallCheck

Hook executed at the end of the installCheck phase.

The distribution phase

The distribution phase is intended to produce a source distribution of the package. The default distPhase first calls make dist, then it copies the resulting source tarballs to $out/tarballs/. This phase is only executed if the attribute doDist is set.

Variables controlling the distribution phase

doDist

If set, the distribution phase is executed.

distTarget

The make target that produces the distribution. Defaults to dist.

distFlags / distFlagsArray

Additional flags passed to make.

tarballs

The names of the source distribution files to be copied to $out/tarballs/. It can contain shell wildcards. The default is *.tar.gz.

dontCopyDist

If set, no files are copied to $out/tarballs/.

preDist

Hook executed at the start of the distribution phase.

postDist

Hook executed at the end of the distribution phase.

Shell functions and utilities

The standard environment provides a number of useful functions.

makeWrapper <executable> <wrapperfile> <args>

Constructs a wrapper for a program with various possible arguments. It is defined as part of 2 setup-hooks named makeWrapper and makeBinaryWrapper that implement the same bash functions. Hence, to use it you have to add makeWrapper to your nativeBuildInputs. Here’s an example usage:

# adds `FOOBAR=baz` to `$out/bin/foo`’s environment
makeWrapper $out/bin/foo $wrapperfile --set FOOBAR baz

# Prefixes the binary paths of `hello` and `git`
# and suffixes the binary path of `xdg-utils`.
# Be advised that paths often should be patched in directly
# (via string replacements or in `configurePhase`).
makeWrapper $out/bin/foo $wrapperfile \
  --prefix PATH : ${lib.makeBinPath [ hello git ]} \
  --suffix PATH : ${lib.makeBinPath [ xdg-utils ]}

Packages may expect or require other utilities to be available at runtime. makeWrapper can be used to add packages to a PATH environment variable local to a wrapper.

Use --prefix to explicitly set dependencies in PATH.

Note

--prefix essentially hard-codes dependencies into the wrapper. They cannot be overridden without rebuilding the package.

If dependencies should be resolved at runtime, use --suffix to append fallback values to PATH.

There’s many more kinds of arguments, they are documented in nixpkgs/pkgs/build-support/setup-hooks/make-wrapper.sh for the makeWrapper implementation and in nixpkgs/pkgs/by-name/ma/makeBinaryWrapper/make-binary-wrapper.sh for the makeBinaryWrapper implementation.

wrapProgram is a convenience function you probably want to use most of the time, implemented by both makeWrapper and makeBinaryWrapper.

Using the makeBinaryWrapper implementation is usually preferred, as it creates a tiny compiled wrapper executable, that can be used as a shebang interpreter. This is needed mostly on Darwin, where shebangs cannot point to scripts, due to a limitation with the execve-syscall. Compiled wrappers generated by makeBinaryWrapper can be inspected with less <path-to-wrapper> - by scrolling past the binary data you should be able to see the shell command that generated the executable and there see the environment variables that were injected into the wrapper.

However, makeWrapper is more flexible and implements more arguments. Use makeWrapper if you need the wrapper to use shell features (e.g. look up environment variables) at runtime.

remove-references-to -t <storepath> [ -t <storepath> … ] <file> …

Removes the references of the specified files to the specified store files. This is done without changing the size of the file by replacing the hash by eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee, and should work on compiled executables. This is meant to be used to remove the dependency of the output on inputs that are known to be unnecessary at runtime. Of course, reckless usage will break the patched programs. To use this, add removeReferencesTo to nativeBuildInputs.

As remove-references-to is an actual executable and not a shell function, it can be used with find. Example removing all references to the compiler in the output:

{
  postInstall = ''
    find "$out" -type f -exec remove-references-to -t ${stdenv.cc} '{}' +
  '';
}

runHook <hook>

Execute <hook> and the values in the array associated with it. The array’s name is determined by removing Hook from the end of <hook> and appending Hooks.

For example, runHook postHook would run the hook postHook and all of the values contained in the postHooks array, if it exists.

substitute <infile> <outfile> <subs>

Performs string substitution on the contents of <infile>, writing the result to <outfile>. The substitutions in <subs> are of the following form:

--replace-fail <s1> <s2>

Replace every occurrence of the string <s1> by <s2>. Will error if no change is made.

--replace-warn <s1> <s2>

Replace every occurrence of the string <s1> by <s2>. Will print a warning if no change is made.

--replace-quiet <s1> <s2>

Replace every occurrence of the string <s1> by <s2>. Will do nothing if no change can be made.

--subst-var <varName>

Replace every occurrence of @varName@ by the contents of the environment variable <varName>. This is useful for generating files from templates, using @...@ in the template as placeholders.

--subst-var-by <varName> <s>

Replace every occurrence of @varName@ by the string <s>.

Example:

substitute ./foo.in ./foo.out \
    --replace-fail /usr/bin/bar $bar/bin/bar \
    --replace-fail "a string containing spaces" "some other text" \
    --subst-var someVar

substituteInPlace <multiple files> <subs>

Like substitute, but performs the substitutions in place on the files passed.

substituteAll <infile> <outfile>

Replaces every occurrence of @varName@, where <varName> is any environment variable, in <infile>, writing the result to <outfile>. For instance, if <infile> has the contents

#! @bash@/bin/sh
PATH=@coreutils@/bin
echo @foo@

and the environment contains bash=/nix/store/bmwp0q28cf21...-bash-3.2-p39 and coreutils=/nix/store/68afga4khv0w...-coreutils-6.12, but does not contain the variable foo, then the output will be

#! /nix/store/bmwp0q28cf21...-bash-3.2-p39/bin/sh
PATH=/nix/store/68afga4khv0w...-coreutils-6.12/bin
echo @foo@

That is, no substitution is performed for undefined variables.

Environment variables that start with an uppercase letter or an underscore are filtered out, to prevent global variables (like HOME) or private variables (like __ETC_PROFILE_DONE) from accidentally getting substituted. The variables also have to be valid bash “names”, as defined in the bash manpage (alphanumeric or _, must not start with a number).

substituteAllInPlace <file>

Like substituteAll, but performs the substitutions in place on the file <file>.

stripHash <path>

Strips the directory and hash part of a store path, outputting the name part to stdout. For example:

# prints coreutils-8.24
stripHash "/nix/store/9s9r019176g7cvn2nvcw41gsp862y6b4-coreutils-8.24"

If you wish to store the result in another variable, then the following idiom may be useful:

name="/nix/store/9s9r019176g7cvn2nvcw41gsp862y6b4-coreutils-8.24"
someVar=$(stripHash $name)

wrapProgram <executable> <makeWrapperArgs>

Convenience function for makeWrapper that replaces <executable> with a wrapper that executes the original program. It takes all the same arguments as makeWrapper, except for --inherit-argv0 (used by the makeBinaryWrapper implementation) and --argv0 (used by both makeWrapper and makeBinaryWrapper wrapper implementations).

If you will apply it multiple times, it will overwrite the wrapper file and you will end up with double wrapping, which should be avoided.

prependToVar <variableName> <elements…>

Prepend elements to a variable.

Example:

$ configureFlags="--disable-static"
$ prependToVar configureFlags --disable-dependency-tracking --enable-foo
$ echo $configureFlags
--disable-dependency-tracking --enable-foo --disable-static

appendToVar <variableName> <elements…>

Append elements to a variable.

Example:

$ configureFlags="--disable-static"
$ appendToVar configureFlags --disable-dependency-tracking --enable-foo
$ echo $configureFlags
--disable-static --disable-dependency-tracking --enable-foo

Package setup hooks

Nix itself considers a build-time dependency as merely something that should previously be built and accessible at build time—packages themselves are on their own to perform any additional setup. In most cases, that is fine, and the downstream derivation can deal with its own dependencies. But for a few common tasks, that would result in almost every package doing the same sort of setup work—depending not on the package itself, but entirely on which dependencies were used.

In order to alleviate this burden, the setup hook mechanism was written, where any package can include a shell script that [by convention rather than enforcement by Nix], any downstream reverse-dependency will source as part of its build process. That allows the downstream dependency to merely specify its dependencies, and lets those dependencies effectively initialize themselves. No boilerplate mirroring the list of dependencies is needed.

The setup hook mechanism is a bit of a sledgehammer though: a powerful feature with a broad and indiscriminate area of effect. The combination of its power and implicit use may be expedient, but isn’t without costs. Nix itself is unchanged, but the spirit of added dependencies being effect-free is violated even if the latter isn’t. For example, if a derivation path is mentioned more than once, Nix itself doesn’t care and makes sure the dependency derivation is already built just the same—depending is just needing something to exist, and needing is idempotent. However, a dependency specified twice will have its setup hook run twice, and that could easily change the build environment (though a well-written setup hook will therefore strive to be idempotent so this is in fact not observable). More broadly, setup hooks are anti-modular in that multiple dependencies, whether the same or different, should not interfere and yet their setup hooks may well do so.

The most typical use of the setup hook is actually to add other hooks which are then run (i.e. after all the setup hooks) on each dependency. For example, the C compiler wrapper’s setup hook feeds itself flags for each dependency that contains relevant libraries and headers. This is done by defining a bash function, and appending its name to one of envBuildBuildHooks, envBuildHostHooks, envBuildTargetHooks, envHostHostHooks, envHostTargetHooks, or envTargetTargetHooks. These 6 bash variables correspond to the 6 sorts of dependencies by platform (there’s 12 total but we ignore the propagated/non-propagated axis).

Packages adding a hook should not hard code a specific hook, but rather choose a variable relative to how they are included. Returning to the C compiler wrapper example, if the wrapper itself is an n dependency, then it only wants to accumulate flags from n + 1 dependencies, as only those ones match the compiler’s target platform. The hostOffset variable is defined with the current dependency’s host offset targetOffset with its target offset, before its setup hook is sourced. Additionally, since most environment hooks don’t care about the target platform, that means the setup hook can append to the right bash array by doing something like

addEnvHooks "$hostOffset" myBashFunction

The existence of setups hooks has long been documented and packages inside Nixpkgs are free to use this mechanism. Other packages, however, should not rely on these mechanisms not changing between Nixpkgs versions. Because of the existing issues with this system, there’s little benefit from mandating it be stable for any period of time.

First, let’s cover some setup hooks that are part of Nixpkgs default stdenv. This means that they are run for every package built using stdenv.mkDerivation, even with custom builders. Some of these are platform specific, so they may run on Linux but not Darwin or vice-versa.

move-docs.sh

This setup hook moves any installed documentation to the /share subdirectory directory. This includes the man, doc and info directories. This is needed for legacy programs that do not know how to use the share subdirectory.

compress-man-pages.sh

This setup hook compresses any man pages that have been installed. The compression is done using the gzip program. This helps to reduce the installed size of packages.

strip.sh

This runs the strip command on installed binaries and libraries. This removes unnecessary information like debug symbols when they are not needed. This also helps to reduce the installed size of packages.

patch-shebangs.sh

This setup hook patches installed scripts to add Nix store paths to their shebang interpreter as found in the build environment. The shebang line tells a Unix-like operating system which interpreter to use to execute the script’s contents.

Note

The generic builder populates PATH from inputs of the derivation.

Invocation

Multiple paths can be specified.

patchShebangs [--build | --host] PATH...
Flags
--build

Look up commands available at build time

--host

Look up commands available at run time

Examples
patchShebangs --host /nix/store/<hash>-hello-1.0/bin
patchShebangs --build configure

#!/bin/sh will be rewritten to #!/nix/store/<hash>-some-bash/bin/sh.

#!/usr/bin/env gets special treatment: #!/usr/bin/env python is rewritten to /nix/store/<hash>/bin/python.

Interpreter paths that point to a valid Nix store location are not changed.

Note

A script file must be marked as executable, otherwise it will not be considered.

This mechanism ensures that the interpreter for a given script is always found and is exactly the one specified by the build.

It can be disabled by setting dontPatchShebangs:

stdenv.mkDerivation {
  # ...
  dontPatchShebangs = true;
  # ...
}

The file patch-shebangs.sh defines the patchShebangs function. It is used to implement patchShebangsAuto, the setup hook that is registered to run during the fixup phase by default.

If you need to run patchShebangs at build time, it must be called explicitly within one of the build phases.

audit-tmpdir.sh

This verifies that no references are left from the install binaries to the directory used to build those binaries. This ensures that the binaries do not need things outside the Nix store. This is currently supported in Linux only.

multiple-outputs.sh

This setup hook adds configure flags that tell packages to install files into any one of the proper outputs listed in outputs. This behavior can be turned off by setting setOutputFlags to false in the derivation environment. See Multiple-output packages for more information.

move-sbin.sh

This setup hook moves any binaries installed in the sbin/ subdirectory into bin/. In addition, a link is provided from sbin/ to bin/ for compatibility.

move-lib64.sh

This setup hook moves any libraries installed in the lib64/ subdirectory into lib/. In addition, a link is provided from lib64/ to lib/ for compatibility.

move-systemd-user-units.sh

This setup hook moves any systemd user units installed in the lib/ subdirectory into share/. In addition, a link is provided from share/ to lib/ for compatibility. This is needed for systemd to find user services when installed into the user profile.

This hook only runs when compiling for Linux.

no-broken-symlinks.sh

This setup hook checks for, reports, and (by default) fails builds when “broken” symlinks are found. A symlink is considered “broken” if it’s dangling (the target doesn’t exist) or reflexive (it refers to itself).

This hook can be disabled by setting dontCheckForBrokenSymlinks.

Note

The hook only considers symlinks with targets inside the Nix store or $TMPDIR directory (typically /nix/store and /build in the builder environment, the later being where build is executed).

Note

The check for reflexivity is direct and does not account for transitivity, so this hook will not prevent cycles in symlinks.

set-source-date-epoch-to-latest.sh

This sets SOURCE_DATE_EPOCH to the modification time of the most recent file.

add-bin-to-path.sh

This setup hook checks if the bin/ directory exists in the $out output path and, if so, adds it to the PATH environment variable. This ensures that executables located in $out/bin are accessible.

This hook is particularly useful during testing, as it allows packages to locate their executables without requiring manual modifications to the PATH.

Note: This hook is specifically designed for the $out/bin directory only and does not handle and support other paths like $sourceRoot/bin. It may not work as intended in cases with multiple outputs or when binaries are located in directories like sbin/. These caveats should be considered when using this hook, as they might introduce unexpected behavior in some specific cases.

writable-tmpdir-as-home.sh

This setup hook ensures that the directory specified by the HOME environment variable is writable. If it is not, the hook assigns HOME to a writable directory (in .home in $NIX_BUILD_TOP). This adjustment is necessary for certain packages that require write access to a home directory.

By setting HOME to a writable directory, this setup hook prevents failures in packages that attempt to write to the home directory.

Bintools Wrapper and hook

The Bintools Wrapper wraps the binary utilities for a bunch of miscellaneous purposes. These are GNU Binutils when targeting Linux, and a mix of cctools and GNU binutils for Darwin. [The “Bintools” name is supposed to be a compromise between “Binutils” and “cctools” not denoting any specific implementation.] Specifically, the underlying bintools package, and a C standard library (glibc or Darwin’s libSystem, just for the dynamic loader) are all fed in, and dependency finding, hardening (see below), and purity checks for each are handled by the Bintools Wrapper. Packages typically depend on CC Wrapper, which in turn (at run time) depends on the Bintools Wrapper.

The Bintools Wrapper was only just recently split off from CC Wrapper, so the division of labor is still being worked out. For example, it shouldn’t care about the C standard library, but just take a derivation with the dynamic loader (which happens to be the glibc on linux). Dependency finding however is a task both wrappers will continue to need to share, and probably the most important to understand. It is currently accomplished by collecting directories of host-platform dependencies (i.e. buildInputs and nativeBuildInputs) in environment variables. The Bintools Wrapper’s setup hook causes any lib and lib64 subdirectories to be added to NIX_LDFLAGS. Since the CC Wrapper and the Bintools Wrapper use the same strategy, most of the Bintools Wrapper code is sparsely commented and refers to the CC Wrapper. But the CC Wrapper’s code, by contrast, has quite lengthy comments. The Bintools Wrapper merely cites those, rather than repeating them, to avoid falling out of sync.

A final task of the setup hook is defining a number of standard environment variables to tell build systems which executables fulfill which purpose. They are defined to just be the base name of the tools, under the assumption that the Bintools Wrapper’s binaries will be on the path. Firstly, this helps poorly-written packages, e.g. ones that look for just gcc when CC isn’t defined yet clang is to be used. Secondly, this helps packages not get confused when cross-compiling, in which case multiple Bintools Wrappers may simultaneously be in use. [6] BUILD_- and TARGET_-prefixed versions of the normal environment variable are defined for additional Bintools Wrappers, properly disambiguating them.

A problem with this final task is that the Bintools Wrapper is honest and defines LD as ld. Most packages, however, firstly use the C compiler for linking, secondly use LD anyways, defining it as the C compiler, and thirdly, only so define LD when it is undefined as a fallback. This triple-threat means Bintools Wrapper will break those packages, as LD is already defined as the actual linker which the package won’t override yet doesn’t want to use. The workaround is to define, just for the problematic package, LD as the C compiler. A good way to do this would be preConfigure = "LD=$CC".

CC Wrapper and hook

The CC Wrapper wraps a C toolchain for a bunch of miscellaneous purposes. Specifically, a C compiler (GCC or Clang), wrapped binary tools, and a C standard library (glibc or Darwin’s libSystem, just for the dynamic loader) are all fed in, and dependency finding, hardening (see below), and purity checks for each are handled by the CC Wrapper. Packages typically depend on the CC Wrapper, which in turn (at run-time) depends on the Bintools Wrapper.

Dependency finding is undoubtedly the main task of the CC Wrapper. This works just like the Bintools Wrapper, except that any include subdirectory of any relevant dependency is added to NIX_CFLAGS_COMPILE. The setup hook itself contains elaborate comments describing the exact mechanism by which this is accomplished.

Similarly, the CC Wrapper follows the Bintools Wrapper in defining standard environment variables with the names of the tools it wraps, for the same reasons described above. Importantly, while it includes a cc symlink to the c compiler for portability, the CC will be defined using the compiler’s “real name” (i.e. gcc or clang). This helps lousy build systems that inspect on the name of the compiler rather than run it.

Here are some more packages that provide a setup hook. Since the list of hooks is extensible, this is not an exhaustive list. The mechanism is only to be used as a last resort, so it might cover most uses.

Other hooks

Many other packages provide hooks, that are not part of stdenv. You can find these in the Hooks Reference.

Compiler and Linker wrapper hooks

If the file ${cc}/nix-support/cc-wrapper-hook exists, it will be run at the end of the compiler wrapper. If the file ${binutils}/nix-support/ld-wrapper-hook exists, it will be run at the end of the linker wrapper, before the linker runs. If the file ${binutils}/nix-support/post-link-hook exists, it will be run at the end of the linker wrapper. These hooks allow a user to inject code into the wrappers. As an example, these hooks can be used to extract extraBefore, params and extraAfter which store all the command line arguments passed to the compiler and linker respectively.

Purity in Nixpkgs

Measures taken to prevent dependencies on packages outside the store, and what you can do to prevent them.

GCC doesn’t search in locations such as /usr/include. In fact, attempts to add such directories through the -I flag are filtered out. Likewise, the linker (from GNU binutils) doesn’t search in standard locations such as /usr/lib. Programs built on Linux are linked against a GNU C Library that likewise doesn’t search in the default system locations.

Hardening in Nixpkgs

There are flags available to harden packages at compile or link-time. These can be toggled using the stdenv.mkDerivation parameters hardeningDisable and hardeningEnable.

Both parameters take a list of flags as strings. The special "all" flag can be passed to hardeningDisable to turn off all hardening. These flags can also be used as environment variables for testing or development purposes.

For more in-depth information on these hardening flags and hardening in general, refer to the Debian Wiki, Ubuntu Wiki, Gentoo Wiki, and the Arch Wiki.

Note that support for some hardening flags varies by compiler, CPU architecture, target OS and libc. Combinations of these that don’t support a particular hardening flag will silently ignore attempts to enable it. To see exactly which hardening flags are being employed in any invocation, the NIX_DEBUG environment variable can be used.

Hardening flags enabled by default

The following flags are enabled by default and might require disabling with hardeningDisable if the program to be packaged is incompatible.

format

Adds the -Wformat -Wformat-security -Werror=format-security compiler options. At present, this warns about calls to printf and scanf functions where the format string is not a string literal and there are no format arguments, as in printf(foo);. This may be a security hole if the format string came from untrusted input and contains %n.

This needs to be turned off or fixed for errors similar to:

/tmp/nix-build-zynaddsubfx-2.5.2.drv-0/zynaddsubfx-2.5.2/src/UI/guimain.cpp:571:28: error: format not a string literal and no format arguments [-Werror=format-security]
         printf(help_message);
                            ^
cc1plus: some warnings being treated as errors

stackprotector

Adds the -fstack-protector-strong --param ssp-buffer-size=4 compiler options. This adds safety checks against stack overwrites rendering many potential code injection attacks into aborting situations. In the best case this turns code injection vulnerabilities into denial of service or into non-issues (depending on the application).

This needs to be turned off or fixed for errors similar to:

bin/blib.a(bios_console.o): In function `bios_handle_cup':
/tmp/nix-build-ipxe-20141124-5cbdc41.drv-0/ipxe-5cbdc41/src/arch/i386/firmware/pcbios/bios_console.c:86: undefined reference to `__stack_chk_fail'

fortify

Adds the -O2 -D_FORTIFY_SOURCE=2 compiler options. During code generation the compiler knows a great deal of information about buffer sizes (where possible), and attempts to replace insecure unlimited length buffer function calls with length-limited ones. This is especially useful for old, crufty code. Additionally, format strings in writable memory that contain %n are blocked. If an application depends on such a format string, it will need to be worked around.

Additionally, some warnings are enabled which might trigger build failures if compiler warnings are treated as errors in the package build. In this case, set env.NIX_CFLAGS_COMPILE to -Wno-error=warning-type.

This needs to be turned off or fixed for errors similar to:

malloc.c:404:15: error: return type is an incomplete type
malloc.c:410:19: error: storage size of 'ms' isn't known

strdup.h:22:1: error: expected identifier or '(' before '__extension__'

strsep.c:65:23: error: register name not specified for 'delim'

installwatch.c:3751:5: error: conflicting types for '__open_2'

fcntl2.h:50:4: error: call to '__open_missing_mode' declared with attribute error: open with O_CREAT or O_TMPFILE in second argument needs 3 arguments

Disabling fortify implies disablement of fortify3

fortify3

Adds the -O2 -D_FORTIFY_SOURCE=3 compiler options. This expands the cases that can be protected by fortify-checks to include some situations with dynamic-length buffers whose length can be inferred at runtime using compiler hints.

Enabling this flag implies enablement of fortify. Disabling this flag does not imply disablement of fortify.

This flag can sometimes conflict with a build-system’s own attempts at enabling fortify support and result in errors complaining about redefinition of _FORTIFY_SOURCE.

pic

Adds the -fPIC compiler options. This options adds support for position independent code in shared libraries and thus making ASLR possible.

Most notably, the Linux kernel, kernel modules and other code not running in an operating system environment like boot loaders won’t build with PIC enabled. The compiler will is most cases complain that PIC is not supported for a specific build.

This needs to be turned off or fixed for assembler errors similar to:

ccbLfRgg.s: Assembler messages:
ccbLfRgg.s:33: Error: missing or invalid displacement expression `private_key_len@GOTOFF'

strictoverflow

Signed integer overflow is undefined behaviour according to the C standard. If it happens, it is an error in the program as it should check for overflow before it can happen, not afterwards. GCC provides built-in functions to perform arithmetic with overflow checking, which are correct and faster than any custom implementation. As a workaround, the option -fno-strict-overflow makes gcc behave as if signed integer overflows were defined.

This flag should not trigger any build or runtime errors.

relro

Adds the -z relro linker option. During program load, several ELF memory sections need to be written to by the linker, but can be turned read-only before turning over control to the program. This prevents some GOT (and .dtors) overwrite attacks, but at least the part of the GOT used by the dynamic linker (.got.plt) is still vulnerable.

This flag can break dynamic shared object loading. For instance, the module systems of Xorg and OpenCV are incompatible with this flag. In almost all cases the bindnow flag must also be disabled and incompatible programs typically fail with similar errors at runtime.

bindnow

Adds the -z now linker option. During program load, all dynamic symbols are resolved, allowing for the complete GOT to be marked read-only (due to relro). This prevents GOT overwrite attacks. For very large applications, this can incur some performance loss during initial load while symbols are resolved, but this shouldn’t be an issue for daemons.

This flag can break dynamic shared object loading. For instance, the module systems of Xorg and PHP are incompatible with this flag. Programs incompatible with this flag often fail at runtime due to missing symbols, like:

intel_drv.so: undefined symbol: vgaHWFreeHWRec

zerocallusedregs

Adds the -fzero-call-used-regs=used-gpr compiler option. This causes the general-purpose registers that an architecture’s calling convention considers “call-used” to be zeroed on return from the function. This can make it harder for attackers to construct useful ROP gadgets and also reduces the chance of data leakage from a function call.

stackclashprotection

This flag adds the -fstack-clash-protection compiler option, which causes growth of a program’s stack to access each successive page in order. This should force the guard page to be accessed and cause an attempt to “jump over” this guard page to crash.

libcxxhardeningfast

Adds the -D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_FAST compiler flag. This flag only has an effect on libc++ targets, and when defined, enables a set of assertions that prevent undefined behavior caused by violating preconditions of the standard library. libc++ provides several hardening modes, and this “fast” mode contains a set of security-critical checks that can be done with relatively little overhead in constant time.

Disabling libcxxhardeningfast implies disablement of checks from libcxxhardeningextensive.

strictflexarrays1

This flag adds the -fstrict-flex-arrays=1 compiler option, which reduces the cases the compiler treats as “flexible arrays” to those declared with length [1], [0] or (the correct) []. This increases the coverage of fortify checks, because such arrays declared as the trailing element of a structure can normally not have their intended length determined by the compiler.

Enabling this flag on packages that still use length declarations of flexible arrays >1 may cause the package to fail to compile citing accesses beyond the bounds of an array or even crash at runtime by detecting an array access as an “overrun”. Few projects still use length declarations of flexible arrays >1.

Disabling strictflexarrays1 implies disablement of strictflexarrays3.

Hardening flags disabled by default

The following flags are disabled by default and should be enabled with hardeningEnable for packages that take untrusted input like network services.

nostrictaliasing

This flag adds the -fno-strict-aliasing compiler option, which prevents the compiler from assuming code has been written strictly following the standard in regards to pointer aliasing and therefore performing optimizations that may be unsafe for code that has not followed these rules.

strictflexarrays3

This flag adds the -fstrict-flex-arrays=3 compiler option, which reduces the cases the compiler treats as “flexible arrays” to only those declared with length as (the correct) []. This increases the coverage of fortify checks, because such arrays declared as the trailing element of a structure can normally not have their intended length determined by the compiler.

Enabling this flag on packages that still use non-empty length declarations for flexible arrays may cause the package to fail to compile citing accesses beyond the bounds of an array or even crash at runtime by detecting an array access as an “overrun”. Many projects still use such non-empty length declarations for flexible arrays.

Enabling this flag implies enablement of strictflexarrays1. Disabling this flag does not imply disablement of strictflexarrays1.

shadowstack

Adds the -fcf-protection=return compiler option. This enables the Shadow Stack feature supported by some newer processors, which maintains a user-inaccessible copy of the program’s stack containing only return-addresses. When returning from a function, the processor compares the return-address value on the two stacks and throws an error if they do not match, considering it a sign of corruption and possible tampering. This should significantly increase the difficulty of ROP attacks.

For the Shadow Stack to be enabled at runtime, all code linked into a process must be built with Shadow Stack enabled, so this is probably only useful to enable on a wide scale, so that all of a packages dependencies also have the feature enabled.

This is currently only supported on some newer Intel and AMD processors as part of the Intel CET set of features. However, the generated code should continue to work on older processors which will simply omit any of this checking.

This breaks some code that does advanced stack management or exception handling. If enabling this hardening flag it is important to test the result on a system that has known working and enabled CET support, so that any such breakage can be discovered.

trivialautovarinit

Adds the -ftrivial-auto-var-init=pattern compiler option. Uninitialized variables generally take on their values based on fragments of previous program state, and attackers can carefully manipulate that state to craft malicious initial values for these variables. This flag causes “trivially-initializable” uninitialized stack variables to be forcibly initialized with a nonzero value that is likely to cause a crash (and therefore be noticed).

Use of this flag is controversial as it can prevent tools that detect uninitialized variable use (such as valgrind) from operating correctly.

This should be turned off or fixed for build errors such as:

sorry, unimplemented: __builtin_clear_padding not supported for variable length aggregates

glibcxxassertions

Adds the -D_GLIBCXX_ASSERTIONS compiler flag. This flag only has an effect on libstdc++ targets, and when defined, enables extra error checking in the form of precondition assertions, such as bounds checking in c++ strings and null pointer checks when dereferencing c++ smart pointers.

These checks may have an impact on performance in some cases.

libcxxhardeningextensive

Adds the -D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_EXTENSIVE compiler flag. This flag only has an effect on libc++ targets, and when defined, enables a set of assertions that prevent undefined behavior caused by violating preconditions of the standard library. libc++ provides several hardening modes, and this “extensive” mode adds checks for undefined behavior that incur relatively little overhead but aren’t security-critical. The additional rigour impacts performance more than fast mode: benchmarking is recommended to determine if it is acceptable for a particular application.

Enabling this flag implies enablement of checks from libcxxhardeningfast. Disabling this flag does not imply disablement of checks from libcxxhardeningfast.

pacret

This flag adds the -mbranch-protection=pac-ret compiler option on aarch64-linux targets. This uses ARM v8.3’s Pointer Authentication feature to sign function return pointers before adding them to the stack. The pointer’s authenticity is then validated before returning to its destination. This dramatically increases the difficulty of ROP exploitation techniques.

This may cause problems with code that does advanced stack manipulation, and debugging/stack-unwinding tools need to be pac-ret aware to work correctly when these features are in operation.

Pre-ARM v8.3 processors will ignore Pointer Authentication instructions, so code built with this flag will continue to work on older processors, though without any of the intended protections. If enabling this flag, it is recommended to ensure the resultant packages are tested against an ARM v8.3+ linux system with known-working Pointer Authentication support so that any breakage caused by this feature is actually detected.



The build platform is ignored because it is a mere implementation detail of the package satisfying the dependency: As a general programming principle, dependencies are always specified as interfaces, not concrete implementation.[1]

Currently, this means for native builds all dependencies are put on the PATH. But in the future that may not be the case for sake of matching cross: the platforms would be assumed to be unique for native and cross builds alike, so only the depsBuild* and nativeBuildInputs would be added to the PATH.[2]

The findInputs function, currently residing in pkgs/stdenv/generic/setup.sh, implements the propagation logic.[3]

It clears the sys_lib_*search_path variables in the Libtool script to prevent Libtool from using libraries in /usr/lib and such.[4]

Eventually these will be passed building natively as well, to improve determinism: build-time guessing, as is done today, is a risk of impurity.[5]

Each wrapper targets a single platform, so if binaries for multiple platforms are needed, the underlying binaries must be wrapped multiple times. As this is a property of the wrapper itself, the multiple wrappings are needed whether or not the same underlying binaries can target multiple platforms.[6]

Meta-attributes

Nix packages can declare meta-attributes that contain information about a package such as a description, its homepage, its license, and so on. For instance, the GNU Hello package has a meta declaration like this:

{
  meta = {
    description = "Program that produces a familiar, friendly greeting";
    longDescription = ''
      GNU Hello is a program that prints "Hello, world!" when you run it.
      It is fully customizable.
    '';
    homepage = "https://www.gnu.org/software/hello/manual/";
    license = lib.licenses.gpl3Plus;
    maintainers = with lib.maintainers; [ eelco ];
    platforms = lib.platforms.all;
  };
}

Meta-attributes are not passed to the builder of the package. Thus, a change to a meta-attribute doesn’t trigger a recompilation of the package.

Standard meta-attributes

If the package is to be submitted to Nixpkgs, please check out the requirements for meta attributes in the contributing documentation.

It is expected that each meta-attribute is one of the following:

description

A short (one-line) description of the package. This is displayed on search.nixos.org.

The general requirements of a description are:

  • Be short, just one sentence.

  • Be capitalized.

  • Not start with definite (“The”) or indefinite (“A”/“An”) article.

  • Not start with the package name.

    • More generally, it should not refer to the package name.

  • Not end with a period (or any punctuation for that matter).

  • Provide factual information.

    • Avoid subjective language.

Wrong: "libpng is a library that allows you to decode PNG images."

Right: "Library for decoding PNG images"

longDescription

An arbitrarily long description of the package in CommonMark Markdown.

branch

Release branch. Used to specify that a package is not going to receive updates that are not in this branch; for example, Linux kernel 3.0 is supposed to be updated to 3.0.X, not 3.1.

homepage

The package’s homepage. Example: https://www.gnu.org/software/hello/manual/

donationPage

The package or project’s donation page, if it exists. Example: https://neovim.io/sponsors/

Authoritative project URLs are preferred.

downloadPage

The page where a link to the current version can be found. Example: https://ftp.gnu.org/gnu/hello/

changelog

A link or a list of links to the location of Changelog for a package. A link may use expansion to refer to the correct changelog version. Example: "https://git.savannah.gnu.org/cgit/hello.git/plain/NEWS?h=v${version}"

license

The license, or licenses, for the package. One from the attribute set defined in nixpkgs/lib/licenses.nix. At this moment using both a list of licenses and a single license is valid. If the license field is in the form of a list representation, then it means that parts of the package are licensed differently. Each license should preferably be referenced by their attribute. The non-list attribute value can also be a space delimited string representation of the contained attribute shortNames or spdxIds. The following are all valid examples:

  • Single license referenced by attribute (preferred) lib.licenses.gpl3Only.

  • Single license referenced by its attribute shortName (frowned upon) "gpl3Only".

  • Single license referenced by its attribute spdxId (frowned upon) "GPL-3.0-only".

  • Multiple licenses referenced by attribute (preferred) with lib.licenses; [ asl20 free ofl ].

  • Multiple licenses referenced as a space delimited string of attribute shortNames (frowned upon) "asl20 free ofl".

For details, see Licenses.

sourceProvenance

A list containing the type or types of source inputs from which the package is built, e.g. original source code, pre-built binaries, etc.

For details, see Source provenance.

maintainers

A list of the maintainers of this Nix expression. Maintainers are defined in nixpkgs/maintainers/maintainer-list.nix. There is no restriction to becoming a maintainer, just add yourself to that list in a separate commit titled “maintainers: add alice” in the same pull request, and reference maintainers with maintainers = with lib.maintainers; [ alice bob ].

teams

A list of the teams of this Nix expression. Teams are defined in nixpkgs/maintainers/team-list.nix, and can be defined in a package with meta.teams = with lib.teams; [ team1 team2 ].

mainProgram

The name of the main binary for the package. This affects the binary nix run executes. Example: "rg"

priority

The priority of the package, used by nix-env to resolve file name conflicts between packages. See the manual page for nix-env for details. Example: "10" (a low-priority package).

platforms

The list of Nix platform types on which the package is supported. Hydra builds packages according to the platform specified. If no platform is specified, the package does not have prebuilt binaries. An example is:

{ meta.platforms = lib.platforms.linux; }

Attribute Set lib.platforms defines various common lists of platforms types.

badPlatforms

The list of Nix platform types on which the package is known not to be buildable. Hydra will never create prebuilt binaries for these platform types, even if they are in meta.platforms. In general it is preferable to set meta.platforms = lib.platforms.all and then exclude any platforms on which the package is known not to build. For example, a package which requires dynamic linking and cannot be linked statically could use this:

{
  meta.platforms = lib.platforms.all;
  meta.badPlatforms = [ lib.systems.inspect.platformPatterns.isStatic ];
}

The lib.meta.availableOn function can be used to test whether or not a package is available (i.e. buildable) on a given platform. Some packages use this to automatically detect the maximum set of features with which they can be built. For example, systemd requires dynamic linking, and has a meta.badPlatforms setting similar to the one above. Packages which can be built with or without systemd support will use lib.meta.availableOn to detect whether or not systemd is available on the hostPlatform for which they are being built; if it is not available (e.g. due to a statically-linked host platform like pkgsStatic) this support will be disabled by default.

timeout

A timeout (in seconds) for building the derivation. If the derivation takes longer than this time to build, Hydra will fail it due to breaking the timeout. However, all computers do not have the same computing power, hence some builders may decide to apply a multiplicative factor to this value. When filling this value in, try to keep it approximately consistent with other values already present in nixpkgs.

meta attributes are not stored in the instantiated derivation. Therefore, this setting may be lost when the package is used as a dependency. To be effective, it must be presented directly to an evaluation process that handles the meta.timeout attribute.

hydraPlatforms

The list of Nix platform types for which the Hydra instance at hydra.nixos.org will build the package. (Hydra is the Nix-based continuous build system.) It defaults to the value of meta.platforms. Thus, the only reason to set meta.hydraPlatforms is if you want hydra.nixos.org to build the package on a subset of meta.platforms, or not at all, e.g.

{
  meta.platforms = lib.platforms.linux;
  meta.hydraPlatforms = [ ];
}

broken

If set to true, the package is marked as “broken”, meaning that it won’t show up in search.nixos.org, and cannot be built or installed unless explicitly allowed. Such unconditionally-broken packages should be removed from Nixpkgs eventually unless they are fixed.

The value of this attribute can depend on a package’s arguments, including stdenv. This means that broken can be used to express constraints, for example:

  • Does not cross compile

    { meta.broken = !(stdenv.buildPlatform.canExecute stdenv.hostPlatform); }
    
  • Broken if all of a certain set of its dependencies are broken

    {
      meta.broken = lib.all (
        map (p: p.meta.broken) [
          glibc
          musl
        ]
      );
    }
    

This makes broken strictly more powerful than meta.badPlatforms. However meta.availableOn currently examines only meta.platforms and meta.badPlatforms, so meta.broken does not influence the default values for optional dependencies.

Underneath, meta.broken = true; is the same as

{
  meta.problems.broken.message = "This package is broken.";
}

By specifying this manually, the error message can be customised.

knownVulnerabilities

A list of known vulnerabilities affecting the package, usually identified by CVE identifiers.

This metadata allows users and tools to be aware of unresolved security issues before using the package, for example:

{
  meta.knownVulnerabilities = [
    "CVE-2024-3094: Malicious backdoor allowing unauthorized remote code execution"
  ];
}

If this list is not empty, the package is marked as “insecure”, meaning that it cannot be built or installed unless the environment variable NIXPKGS_ALLOW_INSECURE is set.

Licenses

The meta.license attribute should preferably contain a value from lib.licenses defined in nixpkgs/lib/licenses.nix, or in-place license description of the same format if the license is unlikely to be useful in another expression.

Although it’s typically better to indicate the specific license, a few generic options are available:

lib.licenses.free, "free"

Catch-all for free software licenses not listed above.

lib.licenses.unfreeRedistributable, "unfree-redistributable"

Unfree package that can be redistributed in binary form. That is, it’s legal to redistribute the output of the derivation. This means that the package can be included in the Nixpkgs channel.

Sometimes proprietary software can only be redistributed unmodified. Make sure the builder doesn’t actually modify the original binaries; otherwise we’re breaking the license. For instance, the NVIDIA X11 drivers can be redistributed unmodified, but our builder applies patchelf to make them work. Thus, its license is "unfree" and it cannot be included in the Nixpkgs channel.

lib.licenses.unfree, "unfree"

Unfree package that cannot be redistributed. You can build it yourself, but you cannot redistribute the output of the derivation. Thus it cannot be included in the Nixpkgs channel.

lib.licenses.unfreeRedistributableFirmware, "unfree-redistributable-firmware"

This package supplies unfree, redistributable firmware. This is a separate value from unfree-redistributable because not everybody cares whether firmware is free.

Source provenance

The value of a package’s meta.sourceProvenance attribute specifies the provenance of the package’s derivation outputs.

If a package contains elements that are not built from the original source by a nixpkgs derivation, the meta.sourceProvenance attribute should be a list containing one or more value from lib.sourceTypes defined in nixpkgs/lib/source-types.nix.

Adding this information helps users who have needs related to build transparency and supply-chain security to gain some visibility into their installed software or set policy to allow or disallow installation based on source provenance.

The presence of a particular sourceType in a package’s meta.sourceProvenance list indicates that the package contains some components falling into that category, though the absence of that sourceType does not guarantee the absence of that category of sourceType in the package’s contents. A package with no meta.sourceProvenance set implies it has no known sourceTypes other than fromSource.

The meaning of the meta.sourceProvenance attribute does not depend on the value of the meta.license attribute.

lib.sourceTypes.fromSource

Package elements which are produced by a nixpkgs derivation which builds them from source code.

lib.sourceTypes.binaryNativeCode

Native code to be executed on the target system’s CPU, built by a third party. This includes packages which wrap a downloaded AppImage or Debian package.

lib.sourceTypes.binaryFirmware

Code to be executed on a peripheral device or embedded controller, built by a third party.

lib.sourceTypes.binaryBytecode

Code to run on a VM interpreter or JIT compiled into bytecode by a third party. This includes packages which download Java .jar files from another source.

lib.sourceTypes.obfuscatedCode

Code which is intentionally obfuscated by a third party, for example by using a code obfuscator or by being distributed in an obfuscated form.

Software identifiers

CPE

Package’s meta.identifiers attribute specifies information about software identifiers associated with this package. Software identifiers are used, for example:

  • to generate Software Bill of Materials (SBOM) that lists all components used to build the software, which can later be used to perform vulnerability or license analysis of the resulting software;

  • to lookup software in different vulnerability databases or report new vulnerabilities to them.

Overriding the default meta.identifiers attribute is optional, but it is recommended to fill in pieces to help tools mentioned above get precise data. For example, we could get automatic notifications about potential vulnerabilities for users in the future. All identifiers specified in meta.identifiers are expected to be unambiguous and valid.

meta.identifiers contains v1 attribute which is an attribute set that guarantees backward compatibility of its constituents. Right now it contains copies of all other attributes in meta.identifiers.

CPE

Common Platform Enumeration (CPE) is a specification maintained by NIST as part of the Security Content Automation Protocol (SCAP). It is used to identify software in National Vulnerabilities Database (NVD, https://nvd.nist.gov) and other vulnerability databases.

Current version of CPE 2.3 consists of 13 parts:

cpe:2.3:a:<vendor>:<product>:<version>:<update>:<edition>:<language>:<sw_edition>:<target_sw>:<target_hw>:<other>

Some of them are as follows:

  • CPE version - current version of CPE is 2.3

  • part - usually in Nixpkgs a for “application”, can also be o for “operating system” or h for “hardware”

  • vendor - can point to the source of the package, or to Nixpkgs itself

  • product - name of the package

  • version - version of the package

  • update - vendor-specific string part of the version string of the latest update (e.g. rc1, beta, etc…)

  • edition - deprecated and should be set to *

You can find information about all of these attributes in the official specification (heading 5.3.3, pages 11-13).

Any fields that don’t have a value are set to either:

  • * (ANY) when the field can match any value

  • - (NA) when the value is not meaningful or not used in the description

For example, for glibc 2.40.1 CPE would be cpe:2.3:a:gnu:glibc:2.40.1:*:*:*:*:*:*:*.

meta.identifiers.cpeParts

This attribute contains an attribute set of all parts of the CPE for this package. Most of the parts default to * (match any value), with some exceptions:

  • part defaults to a (application), can also be set to o for operating systems, for example, Linux kernel, or to h for hardware

  • vendor cannot be deduced from other sources, so it must be specified by the package author

  • product defaults to provided derivation’s pname attribute and must be provided explicitly if pname is missing

  • version and update have no defaults and should be specified explicitly or using helper functions, when missing, cpe attribute will be empty, and all possible guesses using helper functions will be in possibleCPEs attribute.

It is up to the package author to make sure all parts are correct and match expected values in NVD dictionary. Unknown values can be skipped, which would leave them with the default value of *.

Following functions help with filling out version and update fields:

For many packages to make CPE available it should be enough to specify only:

{
  # ...
  meta.identifiers.cpeParts = lib.meta.cpeFullVersionWithVendor vendor version;
}

meta.identifiers.cpe

A readonly attribute that concatenates all CPE parts in one string.

meta.identifiers.possibleCPEs

A readonly attribute containing the list of guesses for what CPE for this package can look like. It includes all variants of version handling mentioned above. Each item is an attrset with attributes cpeParts and cpe for each guess.

Passthru-attributes

Table of Contents

Common passthru-attributes

As opposed to most other mkDerivation input attributes, passthru is not passed to the derivation’s builder executable. Changing it will not trigger a rebuild – it is “passed through”. Its value can be accessed as if it was set inside a derivation.

Note

passthru attributes follow no particular schema, but there are a few conventional patterns.

Example 303. Setting and accessing passthru attributes
{ stdenv, fetchGit }:
let
  hello = stdenv.mkDerivation {
    pname = "hello";
    src = fetchGit {
      # ...
    };

    passthru = {
      foo = "bar";
      baz = {
        value1 = 4;
        value2 = 5;
      };
    };
  };
in
hello.baz.value1
4

Common passthru-attributes

Many passthru attributes are situational, so this section only lists recurring patterns. They fall in one of these categories:

  • Global conventions, which are applied almost universally in Nixpkgs.

    Generally these don’t entail any special support built into the derivation they belong to. Common examples of this type are passthru.tests and passthru.updateScript.

  • Conventions for adding extra functionality to a derivation.

    These tend to entail support from the derivation or the passthru attribute in question. Common examples of this type are passthru.optional-dependencies, passthru.withPlugins, and passthru.withPackages. All of those allow associating the package with a set of components built for that specific package, such as when building Python runtime environments using python.withPackages.

Attributes that apply only to particular build helpers or language ecosystems are documented there.

passthru.tests

An attribute set with tests as values. A test is a derivation that builds when the test passes and fails to build otherwise.

Run these tests with:

$ cd path/to/nixpkgs
$ nix-build -A your-package.tests

Note

The Nixpkgs systems for continuous integration Hydra and nixpkgs-review don’t build these derivations by default, and (@ofborg) only builds them when evaluating pull requests for that particular package, or when manually instructed.

Package tests

Besides tests provided by upstream, that you run in the checkPhase, you may want to define tests derivations in the passthru.tests attribute, which won’t change the build. passthru.tests have several advantages over running tests during any of the standard phases:

  • They access the package as consumers would, independently from the environment in which it was built

  • They can be run and debugged without rebuilding the package, which is useful if that takes a long time

  • They don’t add overhead to each build, as opposed checks added to the installCheckPhase, such as versionCheckHook.

It is also possible to use passthru.tests to test the version with testVersion, but since that is a pretty trivial and recommended thing to do, we recommend using versionCheckHook for that, which has the following advantages over passthru.tests:

  • If the versionCheckPhase (the phase defined by versionCheckHook) fails, it triggers a failure which can’t be ignored if you use the package, or if you find out about it in a nixpkgs-review report.

  • Sometimes packages become silently broken - meaning they fail to launch but their build passes because they don’t perform any tests in the checkPhase. If you use this tool infrequently, such a silent breakage may rot in your system / profile configuration, and you will not notice the failure until you will want to use this package. Testing such basic functionality ensures you have to deal with the failure when you update your system / profile.

  • When you open a PR, ofborg’s CI will run passthru.tests of packages that are directly changed by your PR (according to your commits’ messages), but if you’d want to use the @ofborg build command for dependent packages, you won’t have to specify in addition the .tests attribute of the packages you want to build, and nobody will be able to avoid these tests.

For more on how to write and run package tests for Nixpkgs, see the testing section in the package contributor guide.

NixOS tests

Tests written for NixOS are available as the nixosTests argument to package recipes. For instance, the OpenSMTPD derivation includes lines similar to:

{ nixosTests, ... }:
{
  # ...
  passthru.tests = {
    basic-functionality-and-dovecot-integration = nixosTests.opensmtpd;
  };
}

NixOS tests run in a virtual machine (VM), so they are slower than regular package tests. For more information see the NixOS manual on NixOS module tests.

passthru.updateScript

Nixpkgs tries to automatically update all packages that have an passthru.updateScript attribute. See the section on automatic package updates in the package contributor guide for details.

Multiple-output packages

The Nix language allows a derivation to produce multiple outputs, which is similar to what is utilized by other Linux distribution packaging systems. The outputs reside in separate Nix store paths, so they can be mostly handled independently of each other, including passing to build inputs, garbage collection or binary substitution. The exception is that building from source always produces all the outputs.

The main motivation is to save disk space by reducing runtime closure sizes; consequently also sizes of substituted binaries get reduced. Splitting can be used to have more granular runtime dependencies, for example the typical reduction is to split away development-only files, as those are typically not needed during runtime. As a result, closure sizes of many packages can get reduced to a half or even much less.

Note

The reduction effects could be instead achieved by building the parts in completely separate derivations. That would often additionally reduce build-time closures, but it tends to be much harder to write such derivations, as build systems typically assume all parts are being built at once. This compromise approach of single source package producing multiple binary packages is also utilized often by rpm and deb.

A number of attributes can be used to work with a derivation with multiple outputs. The attribute outputs is a list of strings, which are the names of the outputs. For each of these names, an identically named attribute is created, corresponding to that output.

The attribute meta.outputsToInstall is used to determine the default set of outputs to install when using the derivation name unqualified: bin, or out, or the first specified output; as well as man if that is specified.

Using a split package

In the Nix language the individual outputs can be reached explicitly as attributes, e.g. coreutils.info, but the typical case is just using packages as build inputs.

When a multiple-output derivation gets into a build input of another derivation, the dev output is added if it exists, otherwise the first output is added. In addition to that, propagatedBuildOutputs of that package which by default contain $outputBin and $outputLib are also added. (See the section called “File type groups”.)

In some cases it may be desirable to combine different outputs under a single store path. The symlinkJoin builder can be used to do this. (See the section called “symlinkJoin). Note that this may negate some closure size benefits of using a multiple-output package.

Writing a split derivation

Here you find how to write a derivation that produces multiple outputs.

In nixpkgs there is a framework supporting multiple-output derivations. It tries to cover most cases by default behavior. You can find the source separated in <nixpkgs/pkgs/build-support/setup-hooks/multiple-outputs.sh>; it’s relatively well-readable. The whole machinery is triggered by defining the outputs attribute to contain the list of desired output names (strings).

{
  outputs = [
    "bin"
    "dev"
    "out"
    "doc"
  ];
}

Often such a single line is enough. For each output an equally named environment variable is passed to the builder and contains the path in nix store for that output. Typically you also want to have the main out output, as it catches any files that didn’t get elsewhere.

Note

There is a special handling of the debug output, described at the section called “separateDebugInfo.

“Binaries first”

A commonly adopted convention in nixpkgs is that executables provided by the package are contained within its first output. This convention allows the dependent packages to reference the executables provided by packages in a uniform manner. For instance, provided with the knowledge that the perl package contains a perl executable it can be referenced as ${pkgs.perl}/bin/perl within a Nix derivation that needs to execute a Perl script.

The glibc package is a deliberate single exception to the “binaries first” convention. The glibc has libs as its first output allowing the libraries provided by glibc to be referenced directly (e.g. ${glibc}/lib/ld-linux-x86-64.so.2). The executables provided by glibc can be accessed via its bin attribute (e.g. ${lib.getBin stdenv.cc.libc}/bin/ldd).

The reason for why glibc deviates from the convention is because referencing a library provided by glibc is a very common operation among Nix packages. For instance, third-party executables packaged by Nix are typically patched and relinked with the relevant version of glibc libraries from Nix packages (please see the documentation on patchelf for more details).

File type groups

The support code currently recognizes some particular kinds of outputs and either instructs the build system of the package to put files into their desired outputs or it moves the files during the fixup phase. Each group of file types has an outputFoo variable specifying the output name where they should go. If that variable isn’t defined by the derivation writer, it is guessed – a default output name is defined, falling back to other possibilities if the output isn’t defined.

$outputDev

is for development-only files. These include C(++) headers (include/), pkg-config (lib/pkgconfig/), cmake (lib/cmake/) and aclocal files (share/aclocal/). They go to dev or out by default.

$outputBin

is meant for user-facing binaries, typically residing in bin/. They go to bin or out by default.

$outputLib

is meant for libraries, typically residing in lib/ and libexec/. They go to lib or out by default.

$outputDoc

is for user documentation, typically residing in share/doc/. It goes to doc or out by default.

$outputDevdoc

is for developer documentation. Currently we count gtk-doc and devhelp books, typically residing in share/gtk-doc/ and share/devhelp/, in there. It goes to devdoc or is removed (!) by default. This is because e.g. gtk-doc tends to be rather large and completely unused by nixpkgs users.

$outputMan

is for man pages (except for section 3), typically residing in share/man/man[0-9]/. They go to man or $outputBin by default.

$outputDevman

is for section 3 man pages, typically residing in share/man/man[0-9]/. They go to devman or $outputMan by default.

$outputInfo

is for info pages, typically residing in share/info/. They go to info or $outputBin by default.

Common caveats

  • Some configure scripts don’t like some of the parameters passed by default by the framework, e.g. --docdir=/foo/bar. You can disable this by setting setOutputFlags = false;.

  • The outputs of a single derivation can retain references to each other, but note that circular references are not allowed. (And each strongly-connected component would act as a single output anyway.)

  • Most of split packages contain their core functionality in libraries. These libraries tend to refer to various kind of data that typically gets into out, e.g. locale strings, so there is often no advantage in separating the libraries into lib, as keeping them in out is easier.

  • Some packages have hidden assumptions on install paths, which complicates splitting.

Cross-compilation

Introduction

“Cross-compilation” means compiling a program on one machine for another type of machine. A typical use of cross-compilation is to compile programs for embedded devices that lack the computing power and memory to compile their own programs, but it is useful in many other contexts: producing trusted bootstrap artifacts on Hydra for platforms without physical build hardware, using fast machines (e.g. x86_64) to build for slower architectures popular in routers and switches (e.g. mips/powerpc), and rigorously distinguishing build-time from run-time environments even when developing and deploying on the same machine. Nixpkgs adopts the opinion that packages should be written with cross-compilation in mind, and Nixpkgs should evaluate in a similar way (by minimizing cross-compilation-specific special cases) whether or not one is cross-compiling.

For a hands-on tutorial, see the cross-compilation guide on nix.dev.

This chapter will be organized in three parts. First, it will describe the basics of how to package software in a way that supports cross-compilation. Second, it will describe how to use Nixpkgs when cross-compiling. Third, it will describe the internal infrastructure supporting cross-compilation.

Packaging in a cross-friendly manner

Platform parameters

Nixpkgs follows the conventions of GNU autoconf. We distinguish between 3 types of platforms when building a derivation: build, host, and target. In summary, build is the platform on which a package is being built, host is the platform on which it will run. The third attribute, target, is relevant only for certain specific compilers and build tools.

In Nixpkgs, these three platforms are defined as attribute sets under the names buildPlatform, hostPlatform, and targetPlatform. They are always defined as attributes in the standard environment. That means one can access them like this:

{
  stdenv,
  fooDep,
  barDep,
  ...
}:
{
  # ...stdenv.buildPlatform...
}
buildPlatform

The “build platform” is the platform on which a package is built. Once someone has a built package, or pre-built binary package, the build platform should not matter and can be ignored.

hostPlatform

The “host platform” is the platform on which a package will be run. This is the simplest platform to understand, but also the one with the worst name.

targetPlatform

The “target platform” attribute is, unlike the other two attributes, not actually fundamental to the process of building software. Instead, it is only relevant for compatibility with building certain specific compilers and build tools. It can be safely ignored for all other packages.

The build process of certain compilers is written in such a way that the compiler resulting from a single build can itself only produce binaries for a single platform. The task of specifying this single “target platform” is thus pushed to build time of the compiler. The root cause of this is that the compiler (which will be run on the host) and the standard library/runtime (which will be run on the target) are built by a single build process.

There is no fundamental need to think about a single target ahead of time like this. If the tool supports modular or pluggable backends, both the need to specify the target at build time and the constraint of having only a single target disappear. An example of such a tool is LLVM.

Although the existence of a “target platform” is arguably a historical mistake, it is a common one: examples of tools that suffer from it are GCC, Binutils, GHC and Autoconf. Nixpkgs tries to avoid sharing in the mistake where possible. Still, because the concept of a target platform is so ingrained, it is best to support it as is.

The exact schema these fields follow is a bit ill-defined due to a long and convoluted evolution, but this is slowly being cleaned up. You can see examples of ones used in practice in lib.systems.examples; note how they are not all very consistent. For now, here are few fields can count on them containing:

system

This is a two-component shorthand for the platform. Examples of this would be “x86_64-darwin” and “i686-linux”; see lib.systems.doubles for more. The first component corresponds to the CPU architecture of the platform and the second to the operating system of the platform ([cpu]-[os]). This format has built-in support in Nix, such as the builtins.currentSystem impure string.

config

This is a 3- or 4- component shorthand for the platform. Examples of this would be x86_64-unknown-linux-gnu and aarch64-apple-darwin14. This is a standard format called the “LLVM target triple”, as it was pioneered by LLVM. In the 4-part form, this corresponds to [cpu]-[vendor]-[os]-[abi]. This format is strictly more informative than the “Nix host double”, as the previous format could analogously be termed. This needs a better name than config!

parsed

This is a Nix representation of a parsed LLVM target triple with white-listed components. This can be specified directly, or actually parsed from the config. See lib.systems.parse for the exact representation.

libc

This is a string identifying the standard C library used. Valid identifiers include “glibc” for GNU libc, “libSystem” for Darwin’s Libsystem, and “uclibc” for µClibc. It should probably be refactored to use the module system, like parse.

is*

These predicates are defined in lib.systems.inspect, and slapped onto every platform. They are superior to the ones in stdenv as they force the user to be explicit about which platform they are inspecting. Please use these instead of those.

platform

This is, quite frankly, a dumping ground of ad-hoc settings (it’s an attribute set). See lib.systems.platforms for examples—there’s hopefully one in there that will work verbatim for each platform that is working. Please help us triage these flags and give them better homes!

Using these attributes, the build process of a package can change depending on the situation.

Theory of dependency categorization

Note

This is a rather philosophical description that isn’t very Nixpkgs-specific. For an overview of all the relevant attributes given to mkDerivation, see the section called “Specifying dependencies”. For a description of how everything is implemented, see the section called “Implementation of dependencies”.

In this section we explore the relationship between both runtime and build-time dependencies and the 3 Autoconf platforms.

A run time dependency between two packages requires that their host platforms match. This is directly implied by the meaning of “host platform” and “runtime dependency”: The package dependency exists while both packages are running on a single host platform.

A build time dependency, however, has a shift in platforms between the depending package and the depended-on package. “build time dependency” means that to build the depending package we need to be able to run the depended-on’s package. The depending package’s build platform is therefore equal to the depended-on package’s host platform.

If both the dependency and depending packages aren’t compilers or other machine-code-producing tools, we’re done. And indeed buildInputs and nativeBuildInputs have covered these simpler cases for many years. But if the dependency does produce machine code, we might need to worry about its target platform too. In principle, that target platform might be any of the depending package’s build, host, or target platforms, but we prohibit dependencies from a “later” platform to an earlier platform to limit confusion because we’ve never seen a legitimate use for them.

Finally, if the depending package is a compiler or other machine-code-producing tool, it might need dependencies that run at “emit time”. This is for compilers that (regrettably) insist on being built together with their source languages’ standard libraries. Assuming build != host != target, a run-time dependency of the standard library cannot be run at the compiler’s build time or run time, but only at the run time of code emitted by the compiler.

Putting this all together, that means that we have dependency types of the form X → E, which means that the dependency executes on X and emits code for E; each of X and E can be build, host, or target, and E can be * to indicate that the dependency is not a compiler-like package.

Dependency types describe the relationships that a package has with each of its transitive dependencies. You could think of attaching one or more dependency types to each of the formal parameters at the top of a package’s .nix file, as well as to all of their formal parameters, and so on. Triples like (foo, bar, baz), on the other hand, are a property of an instantiated derivation – you could would attach a triple (mips-linux, mips-linux, sparc-solaris) to a .drv file in /nix/store.

Only nine dependency types matter in practice:

Possible dependency types

Dependency typeDependency’s host platformDependency’s target platform
build → *build(none)
build → buildbuildbuild
build → hostbuildhost
build → targetbuildtarget
host → *host(none)
host → hosthosthost
host → targethosttarget
target → *target(none)
target → targettargettarget

Let’s use g++ as an example to make this table clearer. g++ is a C++ compiler written in C. Suppose we are building g++ with a (build, host, target) platform triple of (foo, bar, baz). This means we are using a foo-machine to build a copy of g++ which will run on a bar-machine and emit binaries for the baz-machine.

  • g++ links against the host platform’s glibc C library, which is a “host→ *” dependency with a triple of (bar, bar, *). Since it is a library, not a compiler, it has no “target”.

  • Since g++ is written in C, the gcc compiler used to compile it is a “build→ host” dependency of g++ with a triple of (foo, foo, bar). This compiler runs on the build platform and emits code for the host platform.

  • gcc links against the build platform’s glibc C library, which is a “build→ *” dependency with a triple of (foo, foo, *). Since it is a library, not a compiler, it has no “target”.

  • This gcc is itself compiled by an earlier copy of gcc. This earlier copy of gcc is a “build→ build” dependency of g++ with a triple of (foo, foo, foo). This “early gcc” runs on the build platform and emits code for the build platform.

  • g++ is bundled with libgcc, which includes a collection of target-machine routines for exception handling and software floating point emulation. libgcc would be a “target→ *” dependency with triple (foo, baz, *), because it consists of machine code which gets linked against the output of the compiler that we are building. It is a library, not a compiler, so it has no target of its own.

  • libgcc is written in C and compiled with gcc. The gcc that compiles it will be a “build→ target” dependency with triple (foo, foo, baz). It gets compiled and run at g++-build-time (on platform foo), but must emit code for the baz-platform.

  • g++ allows inline assembler code, so it depends on access to a copy of the gas assembler. This would be a “host→ target” dependency with triple (foo, bar, baz).

  • g++ (and gcc) include a library libgccjit.so, which wrap the compiler in a library to create a just-in-time compiler. In nixpkgs, this library is in the libgccjit package; if C++ required that programs have access to a JIT, g++ would need to add a “target→ target” dependency for libgccjit with triple (foo, baz, baz). This would ensure that the compiler ships with a copy of libgccjit which both executes on and generates code for the baz-platform.

  • If g++ itself linked against libgccjit.so (for example, to allow compile-time-evaluated C++ expressions), then the libgccjit package used to provide this functionality would be a “host→ host” dependency of g++: it is code which runs on the host and emits code for execution on the host.

Cross packaging cookbook

Some frequently encountered problems when packaging for cross-compilation should be answered here. Ideally, the information above is exhaustive, so this section cannot provide any new information, but it is ludicrous and cruel to expect everyone to spend effort working through the interaction of many features just to figure out the same answer to the same common problem. Feel free to add to this list!

How do I test cross-compilation using emulation?

Every elaborated platform exposes an emulator function on its hostPlatform attribute that returns the path to an emulator capable of running binaries for that platform. The dispatch is defined in lib/systems/default.nix and selects:

  • a no-op exec wrapper, when the build platform can already execute the host platform’s binaries

  • wine for Windows targets

  • qemu-user for foreign Linux targets on a Linux builder

  • wasmtime for WASI

  • nodejs-slim for GHCJS

  • mmix for MMIX

emulator is a function of the package set; emulatorAvailable is a predicate of the same shape that reports whether an emulator exists. Use them from a nix expression rather than invoking qemu by hand, for example inside a checkPhase or passthru.tests derivation:

stdenv.mkDerivation {
  # ...
  doCheck = stdenv.hostPlatform.emulatorAvailable buildPackages;
  checkPhase = ''
    ${stdenv.hostPlatform.emulator buildPackages} ./my-binary --self-test
  '';
}

To run a cross-compiled binary outside the Nix sandbox, build it and invoke the emulator from a shell. This is also a quick way to verify the dispatch table above:

$ nix-build '<nixpkgs>' -A pkgsCross.aarch64-multiplatform.hello # Should be available in cache.nixos.org

To get a path for an emulator, given a crossSystem.config (e.g with aarch64-linux):

$ nix-instantiate --eval --strict -E \
    '(import <nixpkgs> { crossSystem.config = "aarch64-unknown-linux-gnu"; }).stdenv.hostPlatform.emulator (import <nixpkgs> {})'
"/nix/store/.../bin/qemu-aarch64"

And specifically for aarch64-linux, and many other platforms, you have all of them available in qemu package, meaning you can simply run:

$ nix-shell -p qemu --run 'qemu-aarch64 ./result/bin/hello'
Hello, world!

The same pattern works for other targets by substituting the pkgsCross.* attribute and the emulator package (e.g. wine for pkgsCross.mingwW64).

My package fails to find a binutils command (cc/ar/ld etc.)

Many packages assume that an unprefixed binutils (cc/ar/ld etc.) is available, but Nix doesn’t provide one. It only provides a prefixed one, just as it only does for all the other binutils programs. It may be necessary to patch the package to fix the build system to use a prefix. For instance, instead of cc, use ${stdenv.cc.targetPrefix}cc.

{ makeFlags = [ "CC=${stdenv.cc.targetPrefix}cc" ]; }

How do I avoid compiling a GCC cross-compiler from source?

On less powerful machines, it can be inconvenient to cross-compile a package only to find out that GCC has to be compiled from source, which could take up to several hours. Nixpkgs maintains a limited cross-related jobset on Hydra, which tests cross-compilation to various platforms from build platforms “x86_64-linux”, “aarch64-linux”, and “aarch64-darwin”. See pkgs/top-level/release-cross.nix for the full list of target platforms and packages. For instance, the following invocation fetches the pre-built cross-compiled GCC for armv6l-unknown-linux-gnueabihf and builds GNU Hello from source.

$ nix-build '<nixpkgs>' -A pkgsCross.raspberryPi.hello

What if my package’s build system needs to build a C program to be run under the build environment?

Add the following to your mkDerivation invocation.

{ depsBuildBuild = [ buildPackages.stdenv.cc ]; }

My package’s testsuite needs to run host platform code.

Add the following to your mkDerivation invocation.

{ doCheck = stdenv.buildPlatform.canExecute stdenv.hostPlatform; }

Package using Meson needs to run binaries for the host platform during build.

Add mesonEmulatorHook to nativeBuildInputs conditionally on if the target binaries can be executed.

e.g.

{
  nativeBuildInputs = [
    meson
  ]
  ++ lib.optionals (!stdenv.buildPlatform.canExecute stdenv.hostPlatform) [ mesonEmulatorHook ];
}

Example of an error which this fixes.

[Errno 8] Exec format error: './gdk3-scan'

Using -static outside a isStatic platform.

Add stdenv.cc.libc.static (static output of glibc) to buildInputs conditionally on if hostPlatform uses glibc.

e.g.

{
  buildInputs = lib.optionals (stdenv.hostPlatform.libc == "glibc") [ stdenv.cc.libc.static ];
}

Examples of errors which this fixes.

cannot find -lm: No such file or directory

cannot find -lc: No such file or directory

Note

At the time of writing, it is assumed the issue only happens on glibc because it splits the static libraries into a different output.

Note

You may want to look in to using stdenvAdapters.makeStatic or pkgsStatic or a isStatic = true platform.

Cross-building packages

Nixpkgs can be instantiated with localSystem alone, in which case there is no cross-compiling and everything is built by and for that system, or also with crossSystem, in which case packages run on the latter, but all building happens on the former. Both parameters take the same schema as the 3 (build, host, and target) platforms defined in the previous section. As mentioned above, lib.systems.examples has some platforms which are used as arguments for these parameters in practice. You can use them programmatically, or on the command line:

$ nix-build '<nixpkgs>' --arg crossSystem '(import <nixpkgs/lib>).systems.examples.fooBarBaz' -A whatever

Note

Eventually we would like to make these platform examples an unnecessary convenience so that

$ nix-build '<nixpkgs>' --arg crossSystem '{ config = "<arch>-<os>-<vendor>-<abi>"; }' -A whatever

works in the vast majority of cases. The problem today is dependencies on other sorts of configuration which aren’t given proper defaults. We rely on the examples to crudely to set those configuration parameters in some vaguely sane manner on the users behalf. Issue #34274 tracks this inconvenience along with its root cause in crufty configuration options.

While one is free to pass both parameters in full, there’s a lot of logic to fill in missing fields. As discussed in the previous section, only one of system, config, and parsed is needed to infer the other two. Additionally, libc will be inferred from parse. Finally, localSystem.system is also impurely inferred based on the platform evaluation occurs. This means it is often not necessary to pass localSystem at all, as in the command-line example in the previous paragraph.

Note

Many sources (manual, wiki, etc) probably mention passing system, platform, along with the optional crossSystem to Nixpkgs: import <nixpkgs> { system = ..; platform = ..; crossSystem = ..; }. Passing those two instead of localSystem is still supported for compatibility, but is discouraged. Indeed, much of the inference we do for these parameters is motivated by compatibility as much as convenience.

One would think that localSystem and crossSystem overlap horribly with the three *Platforms (buildPlatform, hostPlatform, and targetPlatform; see stage.nix or the manual). Actually, those identifiers are purposefully not used here to draw a subtle but important distinction: While the granularity of having 3 platforms is necessary to properly build packages, it is overkill for specifying the user’s intent when making a build plan or package set. A simple “build vs deploy” dichotomy is adequate: the sliding window principle described in the previous section shows how to interpolate between the these two “end points” to get the 3 platform triple for each bootstrapping stage. That means for any package a given package set, even those not bound on the top level but only reachable via dependencies or buildPackages, the three platforms will be defined as one of localSystem or crossSystem, with the former replacing the latter as one traverses build-time dependencies. A last simple difference is that crossSystem should be null when one doesn’t want to cross-compile, while the *Platforms are always non-null. localSystem is always non-null.

Cross-compilation infrastructure

Implementation of dependencies

The categories of dependencies developed in the section called “Theory of dependency categorization” are specified as lists of derivations given to mkDerivation, as documented in the section called “Specifying dependencies”. In short, each list of dependencies for host → target is called deps<theirHost><theirTarget> (where theirHost, and theirTarget values are either build, host, or target), with exceptions for backwards compatibility that depsBuildHost is instead called nativeBuildInputs and depsHostTarget is instead called buildInputs. Nixpkgs is now structured so that each deps<theirHost><theirTarget> is automatically taken from pkgs<theirHost><theirTarget>. (These pkgs<theirHost><theirTarget>s are quite new, so there is no special case for nativeBuildInputs and buildInputs.) For example, pkgsBuildHost.gcc should be used at build-time, while pkgsHostTarget.openssl should be used at run-time.

Adjacent package sets are defined as pkgs<theirHost><theirTarget> attributes, where “their” represents the new attribute set, and “our” represents the “current” package set. Below is a table of adjacent stages and their aliases. See the section called “Variables specifying dependencies” for usage examples.

Adjacent package setTheir host platformTheir target platform
pkgsBuildBuildOur build platformOur build platform
pkgsBuildHost or buildPackagesOur build platformOur host platform
pkgsBuildTargetOur build platformOur target platform
pkgsHostHostOur host platformOur host platform
pkgsHostTarget or pkgsOur host platformOur target platform
pkgsTargetTarget or targetPackagesOur target platformOur target platform

Now, for most of Nixpkgs’s history, there were no pkgs<theirHost><theirTarget> attributes, and most packages have not been refactored to use it explicitly. Prior to those, there were just buildPackages, pkgs, and targetPackages. Those are now redefined as aliases to pkgsBuildHost, pkgsHostTarget, and pkgsTargetTarget. It is acceptable, even recommended, to use them to show that only their host platform matters. That is, use buildPackages where any of pkgsBuild* would do, and targetPackages when any of pkgsTarget* would do (if we had more than just pkgsTargetTarget).

But before that, there was just pkgs, even though both buildInputs and nativeBuildInputs existed. (Cross barely worked, and those were implemented with some hacks on mkDerivation to override dependencies.) What this means is the vast majority of packages do not use any explicit package set to populate their dependencies, just using whatever callPackage gives them even if they do correctly sort their dependencies into the multiple lists described above. And indeed, asking that users both sort their dependencies, and take them from the right attribute set, is both too onerous and redundant, so the recommended approach (for now) is to continue just categorizing by list and not using an explicit package set.

To make this work, we “splice” together the six pkgs<theirHost><theirTarget> package sets and have callPackage actually take its arguments from that. This is currently implemented in pkgs/top-level/splice.nix. mkDerivation then, for each dependency attribute, pulls the right derivation out from the splice. This splicing can be skipped when not cross-compiling as the package sets are the same, but still is a bit slow for cross-compiling. We’d like to do something better, but haven’t come up with anything yet.

Bootstrapping

Each of the package sets described above come from a single bootstrapping stage. While pkgs/top-level/default.nix, coordinates the composition of stages at a high level, pkgs/top-level/stage.nix “ties the knot” (creates the fixed point) of each stage. The package sets are defined per-stage however, so they can be thought of as edges between stages (the nodes) in a graph. Compositions like pkgsBuildTarget.targetPackages can be thought of as paths to this graph.

While there are many package sets, and thus many edges, the stages can also be arranged in a linear chain. In other words, many of the edges are redundant as far as connectivity is concerned. This hinges on the type of bootstrapping we do. Currently for cross it is:

  1. (native, native, native)

  2. (native, native, foreign)

  3. (native, foreign, foreign)

In each stage, pkgsBuildHost refers to the previous stage, pkgsBuildBuild refers to the one before that, and pkgsHostTarget refers to the current one, and pkgsTargetTarget refers to the next one. When there is no previous or next stage, they instead refer to the current stage. Note how all the invariants regarding the mapping between dependency and depending packages’ build host and target platforms are preserved. pkgsBuildTarget and pkgsHostHost are more complex in that the stage fitting the requirements isn’t always a fixed chain of “prevs” and “nexts” away (modulo the “saturating” self-references at the ends). We just special case each instead. All the primary edges are implemented is in pkgs/stdenv/booter.nix, and secondarily aliases in pkgs/top-level/stage.nix.

Note

The native stages are bootstrapped in legacy ways that predate the current cross implementation. This is why the bootstrapping stages leading up to the final stages are ignored in the previous paragraph.

If one looks at the 3 platform triples, one can see that they overlap such that one could put them together into a chain like:

(native, native, native, foreign, foreign)

If one imagines the saturating self references at the end being replaced with infinite stages, and then overlays those platform triples, one ends up with the infinite tuple:

(native..., native, native, native, foreign, foreign, foreign...)

One can then imagine any sequence of platforms such that there are bootstrap stages with their 3 platforms determined by “sliding a window” that is the 3 tuple through the sequence. This was the original model for bootstrapping. Without a target platform (assume a better world where all compilers are multi-target and all standard libraries are built in their own derivation), this is sufficient. Conversely if one wishes to cross compile “faster”, with a “Canadian Cross” bootstrapping stage where build != host != target, more bootstrapping stages are needed since no sliding window provides the pesky pkgsBuildTarget package set since it skips the Canadian cross stage’s “host”.

Note

It is much better to refer to buildPackages than targetPackages, or more broadly package sets that do not mention “target”. There are three reasons for this.

First, it is because bootstrapping stages do not have a unique targetPackages. For example a (x86-linux, x86-linux, arm-linux) and (x86-linux, x86-linux, x86-windows) package set both have a (x86-linux, x86-linux, x86-linux) package set. Because there is no canonical targetPackages for such a native (build == host == target) package set, we set their targetPackages

Second, it is because this is a frequent source of hard-to-follow “infinite recursions” / cycles. When only package sets that don’t mention target are used, the package set forms a directed acyclic graph. This means that all cycles that exist are confined to one stage. This means they are a lot smaller, and easier to follow in the code or a backtrace. It also means they are present in native and cross builds alike, and so more likely to be caught by CI and other users.

Thirdly, it is because everything target-mentioning only exists to accommodate compilers with lousy build systems that insist on the compiler itself and standard library being built together. Of course that is bad because bigger derivations means longer rebuilds. It is also problematic because it tends to make the standard libraries less like other libraries than they could be, complicating code and build systems alike. Because of the other problems, and because of these innate disadvantages, compilers ought to be packaged another way where possible.

Note

If one explores Nixpkgs, they will see derivations with names like gccCross. Such *Cross derivations is a holdover from before we properly distinguished between the host and target platforms—the derivation with “Cross” in the name covered the build = host != target case, while the other covered the host = target, with build platform the same or not based on whether one was using its .__spliced.buildHost or .__spliced.hostTarget.

Platform Notes

Table of Contents

Darwin (macOS)

Darwin (macOS)

The Darwin stdenv differs from most other ones in Nixpkgs in a few key ways. These differences reflect the default assumptions for building software on that platform. In many cases, you can ignore these differences because the software you are packaging is already written with them in mind. When you do that, write your derivation as normal. You don’t have to include any Darwin-specific special cases. The easiest way to know whether your derivation requires special handling for Darwin is to write it as if it doesn’t and see if it works. If it does, you’re done; skip the rest of this.

  • Darwin uses Clang by default instead of GCC. Packages that refer to $CC or cc should just work in most cases. Some packages may hardcode gcc or g++. You can usually fix that by setting makeFlags = [ "CC=cc" "CXX=C++" ]. If that does not work, you will have to patch the build scripts yourself to use the correct compiler for Darwin.

  • Darwin uses the system libc++ by default to avoid ODR violations and potential compatibility issues from mixing LLVM libc++ with the system libc++. While mixing the two usually worked, the two implementations are not guaranteed to be ABI compatible and are considered distinct by upstream. See the troubleshooting guide below if you need to use newer C++ library features than those supported by the default deployment target.

  • Darwin needs an SDK to build software. The SDK provides a default set of frameworks and libraries to build software, most of which are specific to Darwin. There are multiple versions of the SDK packages in Nixpkgs, but one is included by default in the stdenv. Usually, you don’t have to change or pick a different SDK. When in doubt, use the default.

  • The SDK used by your build can be found using the DEVELOPER_DIR environment variable. There are also versions of this variable available when cross-compiling depending on the SDK’s role. The SDKROOT variable is also set with the path to the SDK’s libraries and frameworks. SDKROOT is always a sub-folder of DEVELOPER_DIR.

  • Darwin includes a platform-specific tool called xcrun to help builds locate binaries they need. A version of xcrun is part of the stdenv on Darwin. If your package invokes xcrun via an absolute path (such as /usr/bin/xcrun), you will need to patch the build scripts to use xcrun instead.

To reiterate: you usually don’t have to worry about this stuff. Start with writing your derivation as if everything is already set up for you (because in most cases it already is). If you run into issues or failures, continue reading below for how to deal with the most common issues you may encounter.

Darwin Issue Troubleshooting

Building a C++ package or library says that certain APIs are unavailable

While some newer APIs may be available via headers only, some require using a system libc++ with the required API support. When that happens, your build will fail because libc++ makes failure to use the correct deployment target an error. To make the newer API available, increase the deployment target to the required version. Note that it is possible to use libc++ from LLVM instead of increasing the deployment target, but it is not recommended. Doing so can cause problems when multiple libc++ implementations are linked into a binary (e.g., from dependencies).

Using a newer deployment target

See below for how to use a newer deployment target. For example, std::print depends on features that are only available on macOS 13.3 or newer. To make them available, set the deployment target to 13.3 using darwinMinVersionHook.

Package fails to build due to missing API availability checks

This is normally a bug in the package or a misconfigured deployment target.

  • If it is using an API from a newer release (e.g., from macOS 26.0 while targeting macOS 14.0), it needs to use an availability check. The code should be patched to use __builtin_available. Note that while the linked documentation is for Objective-C, it is applicable to C and C++ except that you use __builtin_available in place of @available.

  • If the package intends to require the newer platform (i.e., it does not support running on older versions with reduced functionality), use darwinMinVersionHook to set the deployment target to the required version. See below for how to use a newer deployment target.

  • If the package actually handles this through some other mechanism (e.g., MoltenVK relies on the running platform’s MSL version), the error can be suppressed. To suppress the error, add -Wno-error=unguarded-availability to env.NIX_CFLAGS_COMPILE.

Package requires a non-default SDK or fails to build due to missing frameworks or symbols

In some cases, you may have to use a non-default SDK. This can happen when a package requires APIs that are not present in the default SDK. For example, Metal Performance Shaders were added in macOS 12. If the default SDK is 11.3, then a package that requires Metal Performance Shaders will fail to build due to missing frameworks and symbols.

To use a non-default SDK, add it to your derivation’s buildInputs. It is not necessary to override the SDK in the stdenv nor is it necessary to override the SDK used by your dependencies. If your derivation needs a non-default SDK at build time (e.g., for a depsBuildBuild compiler), see the cross-compilation documentation for which input you should use.

When determining whether to use a non-default SDK, consider the following:

  • Try building your derivation with the default SDK. If it works, you’re done.

  • If the package specifies a specific version, use that. See below for how to map Xcode version to SDK version.

  • If the package’s documentation indicates it supports optional features on newer SDKs, consider using the SDK that enables those features. If you’re not sure, use the default SDK.

Note: It is possible to have multiple, different SDK versions in your inputs. When that happens, the one with the highest version is always used.

stdenv.mkDerivation {
  name = "libfoo-1.2.3";
  # ...
  buildInputs = [ apple-sdk_14 ];
}

What is a “deployment target” (or minimum version)?

The “deployment target” refers to the minimum version of macOS that is expected to run an application. In most cases, the default is fine, and you don’t have to do anything else. If you’re not sure, don’t do anything, and that will probably be fine.

Some packages require setting a non-default deployment target (or minimum version) to gain access to certain APIs. You do that using the darwinMinVersionHook, which takes the deployment target version as a parameter. There are primarily two ways to determine the deployment target.

  • The upstream documentation will specify a deployment target or minimum version. Use that.

  • The build will fail because an API requires a certain version. Use that.

  • In all other cases, you probably don’t need to specify a minimum version. The default is usually good enough.

stdenv.mkDerivation {
  name = "libfoo-1.2.3"; # Upstream specifies the minimum supported version as 12.5.
  buildInputs = [ (darwinMinVersionHook "12.5") ];
}

Note: It is possible to have multiple, different instances of darwinMinVersionHook in your inputs. When that happens, the one with the highest version is always used.

Picking an SDK version

The following is a list of Xcode versions, the SDK version in Nixpkgs, and the attribute to use to add it. Check your package’s documentation (platform support or installation instructions) to find which Xcode or SDK version to use. Generally, only the last SDK release for a major version is packaged.

Xcode versionSDK versionNixpkgs attribute
15.0–15.414.4apple-sdk_14 / apple-sdk
16.015.0apple-sdk_15
26.0+26.0+apple-sdk_26, etc

Darwin Default SDK versions

The current default version of the SDK and deployment target (minimum supported version) are indicated by the Darwin-specific platform attributes darwinSdkVersion and darwinMinVersion. Because of the ways that minimum version and SDK can be changed that are not visible to Nix, they should be treated as lower bounds. If you need to parameterize over a specific version, create a function that takes the version as a parameter instead of relying on these attributes.

On macOS, the darwinMinVersion is 14.0, and the darwinSdkVersion is 14.4.

xcrun cannot find a binary

xcrun searches PATH and the SDK’s toolchain for binaries to run. If it cannot find a required binary, it will fail. When that happens, add the package for that binary to your derivation’s nativeBuildInputs (or nativeCheckInputs if the failure is happening when running tests).

stdenv.mkDerivation {
  name = "libfoo-1.2.3";
  # ...
  nativeBuildInputs = [ bison ];
  buildCommand = ''
    xcrun bison foo.y # produces foo.tab.c
    # ...
  '';
}

Package requires xcodebuild

The xcbuild package provides an xcodebuild command for packages that really depend on Xcode. This replacement is not 100% compatible and may run into some issues, but it is able to build many packages. To use xcodebuild, add xcbuildHook to your package’s nativeBuildInputs. It will provide a buildPhase for your derivation. You can use xcbuildFlags to specify flags to xcodebuild such as the required schema. If a schema has spaces in its name, you must set __structuredAttrs to true. See MoltenVK for an example of setting up xcbuild.

stdenv.mkDerivation {
  name = "libfoo-1.2.3";
  xcbuildFlags = [
    "-configuration"
    "Release"
    "-project"
    "libfoo-project.xcodeproj"
    "-scheme"
    "libfoo Package (macOS only)"
  ];
  __structuredAttrs = true;
}
Fixing absolute paths to xcodebuild, xcrun, and PlistBuddy

Many build systems hardcode the absolute paths to xcodebuild, xcrun, and PlistBuddy as /usr/bin/xcodebuild, /usr/bin/xcrun, and /usr/libexec/PlistBuddy respectively. These paths will need to be replaced with relative paths and the xcbuild package if xcodebuild or PListBuddy are used.

stdenv.mkDerivation {
  name = "libfoo-1.2.3";
  postPatch = ''
    substituteInPlace Makefile \
      --replace-fail '/usr/bin/xcodebuild' 'xcodebuild' \
      --replace-fail '/usr/bin/xcrun' 'xcrun' \
      --replace-fail '/usr/bin/PListBuddy' 'PListBuddy'
  '';
}

How to use libiconv on Darwin

The libiconv package is included in the SDK by default along with libresolv and libsbuf. You do not need to do anything to use these packages. They are available automatically. If your derivation needs the iconv binary, add the libiconv package to your nativeBuildInputs (or nativeCheckInputs for tests).

Library install name issues

Libraries on Darwin are usually linked with absolute paths. This is determined by something called an “install name”, which is resolved at link time. Sometimes packages will not set this correctly, causing binaries linking to it not to find their libraries at runtime. This can be fixed by adding extra linker flags or by using install_name_tool to set it in fixupPhase.

Setting the install name via linker flags
stdenv.mkDerivation {
  name = "libfoo-1.2.3";
  # ...
  makeFlags = lib.optional stdenv.hostPlatform.isDarwin "LDFLAGS=-Wl,-install_name,$(out)/lib/libfoo.dylib";
}
Setting the install name using install_name_tool
stdenv.mkDerivation {
  name = "libfoo-1.2.3";
  # ...
  postFixup = ''
    # `-id <install_name>` takes the install name. The last parameter is the path to the library.
    ${stdenv.cc.targetPrefix}install_name_tool -id "$out/lib/libfoo.dylib" "$out/lib/libfoo.dylib"
  '';
}

Even if libraries are linked using absolute paths and resolved via their install name correctly, tests in checkPhase can sometimes fail to run binaries because they are linked against libraries that have not yet been installed. This can usually be solved by running the tests after the installPhase or by using DYLD_LIBRARY_PATH (see dyld(1) for more on setting DYLD_LIBRARY_PATH).

Setting the install name using fixDarwinDylibNames hook

If your package has numerous dylibs needing fixed, while it is preferable to fix the issue in the package’s build, you can update them all by adding the fixDarwinDylibNames hook to your nativeBuildInputs. This hook will scan your package’s outputs for dylibs and correct their install names. Note that if any binaries in your outputs linked those dylibs, you may need to use install_name_tool to replace references to them with the correct paths.

Propagating an SDK (advanced, compilers-only)

The SDK is a package, and it can be propagated. darwinMinVersionHook with a version specified can also be propagated. However, most packages should not do this. The exception is compilers. When you propagate an SDK, it becomes part of your derivation’s public API, and changing the SDK or removing it can be a breaking change. That is why propagating it is only recommended for compilers.

When authoring a compiler derivation, propagate the SDK only for the ways you expect users to use your compiler. Depending on your expected use cases, you may have to do one or all of these.

  • Put it in depsTargetTargetPropagated when your compiler is expected to be added to nativeBuildInputs. That will ensure the SDK is effectively part of the target derivation’s buildInputs.

  • If your compiler uses a hook, put it in the hook’s depsTargetTargetPropagated instead. The effect should be the same as the above.

  • If your package uses the builder pattern, update your builder to add the SDK to the derivation’s buildInputs.

If you’re not sure whether to propagate an SDK, don’t. If your package is a compiler or language, and you’re not sure, ask @NixOS/darwin-maintainers for help deciding.

Dealing with darwin.apple_sdk.frameworks

You may see references to darwin.apple_sdk.frameworks. This is the legacy SDK pattern, and it is being phased out. All packages in darwin.apple_sdk, darwin.apple_sdk_11_0, and darwin.apple_sdk_12_3 have been removed. If your derivation references them, you should delete those references, as the default SDK should be enough to build your package.

Note: the new SDK pattern uses the name apple-sdk to better align with Nixpkgs naming conventions. The legacy SDK pattern uses apple_sdk. You always know you are using the old SDK pattern if the name is apple_sdk.

Some derivations may depend on the location of frameworks in those old packages. To update your derivation to find them in the new SDK, use $SDKROOT instead in preConfigure. For example, if you substitute ${darwin.apple_sdk.frameworks.OpenGL}/Library/Frameworks/OpenGL.framework in postPatch, replace it with $SDKROOT/System/Library/Frameworks/OpenGL.framework in preConfigure.

Note that if your derivation is changing a system path (such as /System/Library/Frameworks/OpenGL.framework), you may be able to remove the path. Compilers and binutils targeting Darwin look for system paths in the SDK sysroot. Some of them (such as Zig or bindgen for Rust) depend on it.

Updating legacy SDK overrides

The legacy SDK provided two ways of overriding the default SDK. They have been removed along with the legacy SDKs.

  • pkgs.darwin.apple_sdk_11_0.callPackage - this pattern was used to provide frameworks from the macOS 11 SDK. It is now the same as callPackage.

  • overrideSDK - this stdenv adapter would try to replace the frameworks used by your derivation and its transitive dependencies. It added the apple-sdk_12 package for 12.3 and did nothing for 11.0. If darwinMinVersion is specified, it would add darwinMinVersionHook with the specified minimum version. No other SDK versions were supported.

Darwin Cross-Compilation

Darwin supports cross-compilation between Darwin platforms. Cross-compilation from Linux is not currently supported but may be supported in the future. To cross-compile to Darwin, you can set crossSystem or use one of the Darwin systems in pkgsCross. The darwinMinVersionHook and the SDKs support cross-compilation. If you need to specify a different SDK version for a depsBuildBuild compiler, add it to your nativeBuildInputs.

stdenv.mkDerivation {
  name = "libfoo-1.2.3";
  # ...
  depsBuildBuild = [ buildPackages.stdenv.cc ];
  nativeBuildInputs = [ apple-sdk_12 ];
  buildInputs = [ apple-sdk_13 ];
  depsTargetTargetPropagated = [ apple-sdk_14 ];
}
# The build-build `clang` will use the 12.3 SDK while the package build itself will use the 13.3 SDK.
# Derivations that add this package as an input will have the 14.4 SDK propagated to them.

The different target SDK and hooks are mangled based on role:

  • DEVELOPER_DIR_FOR_BUILD and MACOSX_DEPLOYMENT_TARGET_FOR_BUILD for the build platform;

  • DEVELOPER_DIR and MACOSX_DEPLOYMENT_TARGET for the host platform; and

  • DEVELOPER_DIR_FOR_TARGET and MACOSX_DEPLOYMENT_TARGET_FOR_TARGET for the build platform.

In static compilation situations, it is possible for the build and host platform to be the same platform but have different SDKs with the same version (one dynamic and one static). cc-wrapper and bintools-wrapper take care of handling this distinction.

Toolchains

Table of Contents

The LLVM Toolchain

The LLVM Toolchain

Table of Contents

Using LLVM

LLVM is a target-independent optimizer and code generator and serves as the basis for many compilers such as Haskell’s GHC, rustc, Zig, and many others. It forms the base tools for Apple’s Darwin platform.

Using LLVM

LLVM has two ways of being used. One is by using it across all of Nixpkgs and the other is to compile and build individual packages.

Building packages with LLVM

Nixpkgs supports two methods of compiling the world with LLVM. One is via setting useLLVM in crossSystem while importing. This is the recommended way when cross compiling as it is more expressive. An example of doing aarch64-linux cross compilation from x86_64-linux with LLVM on the target is the following:

import <nixpkgs> {
  localSystem = {
    system = "x86_64-linux";
  };
  crossSystem = {
    useLLVM = true;
    linker = "lld";
  };
}

Note that we set linker to lld. This is because LLVM has its own linker, called “lld”. By setting it, we utilize Clang and lld within this new instance of Nixpkgs. There is a shorthand method for building everything with LLVM: pkgsLLVM. This is easier to use with nix-build (or nix build):

nix-build -A pkgsLLVM.hello

This will compile the GNU hello package with LLVM and the lld linker like previously mentioned.

Using clangStdenv

Another simple way is to override the stdenv with clangStdenv. This causes a single package to be built with Clang. However, this stdenv does not override platform defaults to use compiler-rt, libc++, and libunwind. This is the preferred way to make a single package in Nixpkgs build with Clang. There are cases where just Clang isn’t enough. For these situations, there is libcxxStdenv, which uses Clang with libc++ and compiler-rt.

Build helpers

A build helper is a function that produces derivations.

Warning

This is not to be confused with the builder argument of the Nix derivation primitive, which refers to the executable that produces the build result, or remote builder, which refers to a remote machine that could run such an executable.

Such a function is usually designed to abstract over a typical workflow for a given programming language or framework. This allows declaring a build recipe by setting a limited number of options relevant to the particular use case instead of using the derivation function directly.

stdenv.mkDerivation is the most widely used build helper and serves as a basis for many others. In addition, it offers various options to customize parts of the builds.

There is no uniform interface for build helpers. Trivial build helpers and fetchers have various input types for convenience. Language- or framework-specific build helpers usually follow the style of stdenv.mkDerivation, which accepts an attribute set or a fixed-point function taking an attribute set.

Fixed-point arguments of build helpers

As mentioned in the beginning of this part, stdenv.mkDerivation could alternatively accept a fixed-point function. The input of this function, typically named finalAttrs, is expected to be the final state of the attribute set. A build helper like this is said to accept fixed-point arguments.

Build helpers don’t always support fixed-point arguments yet, as support in stdenv.mkDerivation was first included in Nixpkgs 22.05.

Defining a build helper with lib.extendMkDerivation

Developers can use the Nixpkgs library function lib.customisation.extendMkDerivation to define a build helper supporting fixed-point arguments from an existing one with such support, with an attribute overlay similar to the one taken by <pkg>.overrideAttrs.

Besides overriding, lib.extendMkDerivation also supports excludeDrvArgNames to optionally exclude some arguments in the input fixed-point arguments from passing down to the base build helper (specified as constructDrv).

Example 304. Example definition of mkLocalDerivation extended from stdenv.mkDerivation with lib.extendMkDerivation

We want to define a build helper named mkLocalDerivation that builds locally without using substitutes by default.

Instead of taking a plain attribute set,

{
  preferLocalBuild ? true,
  allowSubstitute ? false,
  specialArg ? (_: false),
  ...
}@args:

stdenv.mkDerivation (
  removeAttrs [
    # Don't pass specialArg into mkDerivation.
    "specialArg"
  ] args
  // {
    # Arguments to pass
    inherit preferLocalBuild allowSubstitute;
    # Some expressions involving specialArg
    greeting = if specialArg "hi" then "hi" else "hello";
  }
)

we could define with lib.extendMkDerivation an attribute overlay to make the result build helper also accept the attribute set’s fixed point passing to the underlying stdenv.mkDerivation, named finalAttrs here:

lib.extendMkDerivation {
  constructDrv = stdenv.mkDerivation;
  excludeDrvArgNames = [
    # Don't pass specialArg into mkDerivation.
    "specialArg"
  ];
  extendDrvArgs =
    finalAttrs:
    {
      preferLocalBuild ? true,
      allowSubstitute ? false,
      specialArg ? (_: false),
      ...
    }@args:
    {
      # Arguments to pass
      inherit preferLocalBuild allowSubstitute;
      # Some expressions involving specialArg
      greeting = if specialArg "hi" then "hi" else "hello";
    };
}

If one needs to apply extra changes to the result derivation, pass the derivation transformation function to lib.extendMkDerivation as lib.customisation.extendMkDerivation { transformDrv = drv: ...; }.

Fetchers

Building software with Nix often requires downloading source code and other files from the internet. To this end, we use functions that we call fetchers, which obtain remote sources via various protocols and services.

Nix provides built-in fetchers such as fetchTarball. Nixpkgs provides its own fetchers, which work differently:

  • A built-in fetcher will download and cache files at evaluation time and produce a store path. A Nixpkgs fetcher will create a (fixed-output) derivation, and files are downloaded at build time.

  • Built-in fetchers will invalidate their cache after tarball-ttl expires, and will require network activity to check if the cache entry is up to date. Nixpkgs fetchers only re-download if the specified hash changes or the store object is not available.

  • Built-in fetchers do not use substituters. Derivations produced by Nixpkgs fetchers will use any configured binary cache transparently.

This significantly reduces the time needed to evaluate Nixpkgs, and allows Hydra to retain and re-distribute sources used by Nixpkgs in the public binary cache. For these reasons, Nix’s built-in fetchers are not allowed in Nixpkgs.

The following table summarises the differences:

FetchersDownloadOutputCacheRe-download when
builtins.fetch*evaluation timestore path/nix/store, ~/.cache/nixtarball-ttl expires, cache miss in ~/.cache/nix, output store object not in local store
pkgs.fetch*build timederivation/nix/store, substitutersoutput store object not available

Tip

pkgs.fetchFrom* helpers retrieve snapshots of version-controlled sources, as opposed to the entire version history, which is more efficient. pkgs.fetchgit by default also has the same behaviour, but can be changed through specific attributes given to it.

Caveats

Because Nixpkgs fetchers are fixed-output derivations, an output hash has to be specified, usually indirectly through a hash attribute. This hash refers to the derivation output, which can be different from the remote source itself!

This has the following implications that you should be aware of:

  • Use Nix (or Nix-aware) tooling to produce the output hash.

  • When changing any fetcher parameters, always update the output hash. Use one of the methods from the section called “Updating source hashes”. Otherwise, existing store objects that match the output hash will be re-used rather than fetching new content.

    Note

    A similar problem arises while testing changes to a fetcher’s implementation. If the output of the derivation already exists in the Nix store, test failures can go undetected. The invalidateFetcherByDrvHash function helps prevent reusing cached derivations.

Updating source hashes

There are several ways to obtain the hash corresponding to a remote source. Unless you understand how the fetcher you’re using calculates the hash from the downloaded contents, you should use the fake hash method.

  1. The fake hash method: In your package recipe, set the hash to one of

    • ""

    • lib.fakeHash

    • lib.fakeSha256

    • lib.fakeSha512

    Attempt to build, extract the calculated hashes from error messages, and put them into the recipe.

    Warning

    You must use one of these four fake hashes and not some arbitrarily-chosen hash. See the section called “Obtaining hashes securely” for details.

    Example 305. Update source hash with the fake hash method

    Consider the following recipe that produces a plain file:

    { fetchurl }:
    fetchurl {
      url = "https://raw.githubusercontent.com/NixOS/nixpkgs/23.05/.version";
      hash = "sha256-ZHl1emidXVojm83LCVrwULpwIzKE/mYwfztVkvpruOM=";
    }
    

    A common mistake is to update a fetcher parameter, such as url, without updating the hash:

    { fetchurl }:
    fetchurl {
      url = "https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/.version";
      hash = "sha256-ZHl1emidXVojm83LCVrwULpwIzKE/mYwfztVkvpruOM=";
    }
    

    This will produce the same output as before! Set the hash to an empty string:

    { fetchurl }:
    fetchurl {
      url = "https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/.version";
      hash = "";
    }
    

    When building the package, use the error message to determine the correct hash:

    $ nix-build
    (some output removed for clarity)
    error: hash mismatch in fixed-output derivation '/nix/store/7yynn53jpc93l76z9zdjj4xdxgynawcw-version.drv':
            specified: sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
                got:    sha256-BZqI7r0MNP29yGH5+yW2tjU9OOpOCEvwWKrWCv5CQ0I=
    error: build of '/nix/store/bqdjcw5ij5ymfbm41dq230chk9hdhqff-version.drv' failed
    

  2. Prefetch the source with nix-prefetch-<type> <URL>, where <type> is one of

    • url

    • git

    • hg

    • cvs

    • bzr

    • svn

    • darcs

    • pijul

    The hash is printed to stdout.

  3. Prefetch by package source (with nix-prefetch-url '<nixpkgs>' -A <package>.src, where <package> is package attribute name). The hash is printed to stdout.

    This works well when you’ve upgraded the existing package version and want to find out new hash, but is useless if the package can’t be accessed by attribute or the package has multiple sources (.srcs, architecture-dependent sources, etc).

  4. Upstream hash: use it when upstream provides sha256 or sha512. Don’t use it when upstream provides md5, compute sha256 instead.

    A little nuance is that nix-prefetch-* tools produce hashes with the nix32 encoding (a Nix-specific base32 adaptation), but upstream usually provides hexadecimal (base16) encoding. Fetchers understand both formats. Nixpkgs does not standardise on any one format.

    You can convert between hash formats with nix-hash.

  5. Extract the hash from a local source archive with sha256sum. Use nix-prefetch-url file:///path/to/archive if you want the custom Nix base32 hash.

Obtaining hashes securely

It’s always a good idea to avoid Man-in-the-Middle (MITM) attacks when downloading source contents. Otherwise, you could unknowingly download malware instead of the intended source, and instead of the actual source hash, you’ll end up using the hash of malware. Here are security considerations for this scenario:

  • http:// URLs are not secure to prefetch hashes.

  • Upstream hashes should be obtained via a secure protocol.

  • https:// URLs give you more protections when using nix-prefetch-* or for upstream hashes.

  • https:// URLs are secure when using the fake hash method only if you use one of the listed fake hashes. If you use any other hash, the download will be exposed to MITM attacks even if you use HTTPS URLs.

    In more concrete terms, if you use any other hash, the --insecure flag will be passed to the underlying call to curl when downloading content.

Proxy usage

Nixpkgs fetchers can make use of a http(s) proxy. Each fetcher will automatically inherit proxy-related environment variables (http_proxy, https_proxy, etc) via impureEnvVars.

The environment variable NIX_SSL_CERT_FILE is also inherited in fetchers, and can be used to provide a custom certificate bundle to fetchers. This is usually required for a https proxy to work without certificate validation errors.

To use a temporary Tor instance as a proxy for fetching from .onion addresses, add nativeBuildInputs = [ tor.proxyHook ]; to the fetcher parameters.

fetchurl

fetchurl returns a fixed-output derivation which downloads content from a given URL and stores the unaltered contents within the Nix store.

It uses curl(1) internally, and allows its behaviour to be modified by specifying a few attributes in the argument to fetchurl (see the documentation for attributes curlOpts, curlOptsList, and netrcPhase).

The resulting store path is determined by the hash given to fetchurl, and also the name (or pname and version) values.

If neither name nor pname and version are specified when calling fetchurl, it will default to using the basename of url or the first element of urls. If pname and version are specified, fetchurl will use those values and will ignore name, even if it is also specified.

Inputs

fetchurl requires an attribute set with the following attributes:

url (String; optional)

The URL to download from.

Note

Either url or urls must be specified, but not both.

All URLs of the format specified here are supported.

Default value: "".

urls (List of String; optional)

A list of URLs, specifying download locations for the same content. Each URL will be tried in order until one of them succeeds with some content or all of them fail. See Example 307 to understand how this attribute affects the behaviour of fetchurl.

Note

Either url or urls must be specified, but not both.

Default value: [].

hash (String; optional)

Hash of the derivation output of fetchurl, following the format for integrity metadata as defined by SRI. For more information, see the section called “Caveats”.

Note

It is recommended that you use the hash attribute instead of the other hash-specific attributes that exist for backwards compatibility.

If hash is not specified, you must specify outputHash and outputHashAlgo, or one of sha512, sha256, or sha1.

Default value: "".

outputHash (String; optional)

Hash of the derivation output of fetchurl in the format expected by Nix. See the documentation on the Nix manual for more information about its format.

Note

It is recommended that you use the hash attribute instead.

If outputHash is specified, you must also specify outputHashAlgo.

Default value: "".

outputHashAlgo (String; optional)

Algorithm used to generate the value specified in outputHash. See the documentation on the Nix manual for more information about the values it supports.

Note

It is recommended that you use the hash attribute instead.

The value specified in outputHashAlgo will be ignored if outputHash isn’t also specified.

Default value: "".

sha1 (String; optional)

SHA-1 hash of the derivation output of fetchurl in the format expected by Nix. See the documentation on the Nix manual for more information about its format.

Note

It is recommended that you use the hash attribute instead.

Default value: "".

sha256 (String; optional)

SHA-256 hash of the derivation output of fetchurl in the format expected by Nix. See the documentation on the Nix manual for more information about its format.

Note

It is recommended that you use the hash attribute instead.

Default value: "".

sha512 (String; optional)

SHA-512 hash of the derivation output of fetchurl in the format expected by Nix. See the documentation on the Nix manual for more information about its format.

Note

It is recommended that you use the hash attribute instead.

Default value: "".

name (String; optional)

The symbolic name of the downloaded file when saved in the Nix store. See the fetchurl overview for details on how the name of the file is decided.

Default value: "".

pname (String; optional)

A base name, which will be combined with version to form the symbolic name of the downloaded file when saved in the Nix store. See the fetchurl overview for details on how the name of the file is decided.

Note

If pname is specified, you must also specify version, otherwise fetchurl will ignore the value of pname.

Default value: "".

version (String; optional)

A version, which will be combined with pname to form the symbolic name of the downloaded file when saved in the Nix store. See the fetchurl overview for details on how the name of the file is decided.

Default value: "".

recursiveHash (Boolean; optional)

If set to true, will signal to Nix that the hash given to fetchurl was calculated using the "recursive" mode. See the documentation on the Nix manual for more information about the existing modes.

By default, fetchurl uses "recursive" mode when the executable attribute is set to true, so you don’t need to specify recursiveHash in this case.

Default value: false.

executable (Boolean; optional)

If true, sets the executable bit on the downloaded file.

Default value: false.

downloadToTemp (Boolean; optional)

If true, saves the downloaded file to a temporary location instead of the expected Nix store location. This is useful when used in conjunction with postFetch attribute, otherwise fetchurl will not produce any meaningful output.

The location of the downloaded file will be set in the $downloadedFile variable, which should be used by the script in the postFetch attribute. See Example 308 to understand how to work with this attribute.

Default value: false.

postFetch (String; optional)

Script executed after the file has been downloaded successfully, and before fetchurl finishes running. Useful for post-processing, to check or transform the file in some way. See Example 308 to understand how to work with this attribute.

Default value: "".

netrcPhase (String or Null; optional)

Script executed to create a netrc(5) file to be used with curl(1). The script should create the netrc file (note that it does not begin with a “.”) in the directory it’s currently running in ($PWD).

The script is executed during the setup done by fetchurl before it runs any of its code to download the specified content.

Note

If specified, fetchurl will automatically alter its invocation of curl(1) to use the netrc file, so you don’t need to add anything to curlOpts or curlOptsList.

Caution

Since netrcPhase needs to be specified in your source Nix code, any secrets that you put directly in it will be world-readable by design (both in your source code, and when the derivation gets created in the Nix store).

If you want to avoid this behaviour, see the documentation of netrcImpureEnvVars for an alternative way of dealing with these secrets.

Default value: null.

netrcImpureEnvVars (List of String; optional)

If specified, fetchurl will add these environment variable names to the list of impure environment variables, which will be passed from the environment of the calling user to the builder running the fetchurl code.

This is useful when used with netrcPhase to hide any secrets that are used in it, because the script in netrcPhase only needs to reference the environment variables with the secrets in them instead. However, note that these are called impure variables for a reason: the environment that starts the build needs to have these variables declared for everything to work properly, which means that additional setup is required outside what Nix controls.

Default value: [].

curlOpts (String; optional)

If specified, this value will be appended to the invocation of curl(1) when downloading the URL(s) given to fetchurl. Multiple arguments can be separated by spaces normally, but values with whitespaces will be interpreted as multiple arguments (instead of a single value), even if the value is escaped. See curlOptsList for a way to pass values with whitespaces in them.

Default value: "".

curlOptsList (List of String; optional)

If specified, each element of this list will be passed as an argument to the invocation of curl(1) when downloading the URL(s) given to fetchurl. This allows passing values that contain spaces, with no escaping needed.

Default value: [].

showURLs (Boolean; optional)

If set to true, this will stop fetchurl from downloading anything at all. Instead, it will output a list of all the URLs it would’ve used to download the content (after resolving mirror:// URLs, for example). This is useful for debugging.

Default value: false.

meta (Attribute Set; optional)

Specifies any meta-attributes for the derivation returned by fetchurl.

Default value: {}.

passthru (Attribute Set; optional)

Specifies any extra passthru attributes for the derivation returned by fetchurl. Note that fetchurl defines passthru attributes of its own. Attributes specified in passthru can override the default attributes returned by fetchurl.

Default value: {}.

preferLocalBuild (Boolean; optional)

This is the same attribute as defined in the Nix manual. It is true by default because making a remote machine download the content just duplicates network traffic (since the local machine might download the results from the derivation anyway), but this could be useful in cases where network access is restricted on local machines.

Default value: true.

nativeBuildInputs (List of Attribute Set; optional)

Additional packages needed to download the content. This is useful if you need extra packages for postFetch or netrcPhase, for example. Has the same semantics as in the section called “nativeBuildInputs. See Example 308 to understand how this can be used with postFetch.

Default value: [].

Passthru outputs

fetchurl also defines its own passthru attributes:

url (String)

The same url attribute passed in the argument to fetchurl.

Examples

Example 306. Using fetchurl to download a file

The following package downloads a small file from a URL and shows the most common way to use fetchurl:

{ fetchurl }:
fetchurl {
  url = "https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/.version";
  hash = "sha256-BZqI7r0MNP29yGH5+yW2tjU9OOpOCEvwWKrWCv5CQ0I=";
}

After building the package, the file will be downloaded and placed into the Nix store:

$ nix-build
(output removed for clarity)
/nix/store/4g9y3x851wqrvim4zcz5x2v3zivmsq8n-version

$ cat /nix/store/4g9y3x851wqrvim4zcz5x2v3zivmsq8n-version
23.11

Example 307. Using fetchurl to download a file with multiple possible URLs

The following package adapts Example 306 to use multiple URLs. The first URL was crafted to intentionally return an error to illustrate how fetchurl will try multiple URLs until it finds one that works (or all URLs fail).

{ fetchurl }:
fetchurl {
  urls = [
    "https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/does-not-exist"
    "https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/.version"
  ];
  hash = "sha256-BZqI7r0MNP29yGH5+yW2tjU9OOpOCEvwWKrWCv5CQ0I=";
}

After building the package, both URLs will be used to download the file:

$ nix-build
(some output removed for clarity)
trying https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/does-not-exist
(some output removed for clarity)
curl: (22) The requested URL returned error: 404

trying https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/.version
(some output removed for clarity)
/nix/store/n9asny31z32q7sdw6a8r1gllrsfy53kl-does-not-exist

$ cat /nix/store/n9asny31z32q7sdw6a8r1gllrsfy53kl-does-not-exist
23.11

However, note that the name of the file was derived from the first URL (this is further explained in the fetchurl overview). To ensure the result will have the same name regardless of which URLs are used, we can modify the package:

{ fetchurl }:
fetchurl {
  name = "nixpkgs-version";
  urls = [
    "https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/does-not-exist"
    "https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/.version"
  ];
  hash = "sha256-BZqI7r0MNP29yGH5+yW2tjU9OOpOCEvwWKrWCv5CQ0I=";
}

After building the package, the result will have the name we specified:

$ nix-build
(output removed for clarity)
/nix/store/zczb6wl3al6jm9sm5h3pr6nqn0i5ji9z-nixpkgs-version

Example 308. Manipulating the content downloaded by fetchurl

It might be useful to manipulate the content downloaded by fetchurl directly in its derivation. In this example, we’ll adapt Example 306 to append the result of running the hello package to the contents we download, purely to illustrate how to manipulate the content.

{
  fetchurl,
  hello,
  lib,
}:
fetchurl {
  url = "https://raw.githubusercontent.com/NixOS/nixpkgs/23.11/.version";

  nativeBuildInputs = [ hello ];

  downloadToTemp = true;
  postFetch = ''
    hello >> "$downloadedFile"
    mv "$downloadedFile" "$out"
  '';

  hash = "sha256-ceooQQYmDx5+0nfg40uU3NNI2yKrixP7HZ/xLZUNv+w=";
}

After building the package, the resulting file will have “Hello, world!” appended to it:

$ nix-build
(output removed for clarity)
/nix/store/ifi6pp7q0ag5h7c5v9h1c1c7bhd10c7f-version

$ cat /nix/store/ifi6pp7q0ag5h7c5v9h1c1c7bhd10c7f-version
23.11
Hello, world!

Note that the hash specified in the package is different than the hash specified in Example 306, because the contents of the output have changed (even though the actual file that was downloaded is the same). See the section called “Caveats” for more details on how to work with the hash attribute when the output changes.


fetchzip

Returns a fixed-output derivation which downloads an archive from a given URL and decompresses it.

Despite its name, fetchzip is not limited to .zip files but can also be used with various compressed tarball formats by default. This can be extended by specifying additional attributes, see Example 310 to understand how to do that.

Inputs

fetchzip requires an attribute set, and most attributes are passed to the underlying call to fetchurl.

The attributes below are treated differently by fetchzip when compared to what fetchurl expects:

name (String; optional)

Works as defined in fetchurl, but has a different default value than fetchurl.

Default value: "source".

nativeBuildInputs (List of Attribute Set; optional)

Works as defined in fetchurl, but it is also augmented by fetchzip to include packages to deal with additional archives (such as .zip).

Default value: [].

postFetch (String; optional)

Works as defined in fetchurl, but it is also augmented with the code needed to make fetchzip work.

Caution

It is only safe to modify files in $out in postFetch. Consult the implementation of fetchzip for anything more involved.

Default value: "".

stripRoot (Boolean; optional)

If true, the decompressed contents are moved one level up the directory tree.

This is useful for archives that decompress into a single directory which commonly includes some values that change with time, such as version numbers. When this is the case (and stripRoot is true), fetchzip will remove this directory and make the decompressed contents available in the top-level directory.

Example 309 shows what this attribute does.

This attribute is not passed through to fetchurl.

Default value: true.

extension (String or Null; optional)

If set, the archive downloaded by fetchzip will be renamed to a filename with the extension specified in this attribute.

This is useful when making fetchzip support additional types of archives, because the implementation may use the extension of an archive to determine whether they can decompress it. If the URL you’re using to download the contents doesn’t end with the extension associated with the archive, use this attribute to fix the filename of the archive.

This attribute is not passed through to fetchurl.

Default value: null.

recursiveHash (Boolean; optional)

Works as defined in fetchurl, but its default value is different than for fetchurl.

Default value: true.

downloadToTemp (Boolean; optional)

Works as defined in fetchurl, but its default value is different than for fetchurl.

Default value: true.

extraPostFetch DEPRECATED

This attribute is deprecated. Please use postFetch instead.

This attribute is not passed through to fetchurl.

Examples

Example 309. Using fetchzip to output contents directly

The following recipe shows how to use fetchzip to decompress a .tar.gz archive:

{ fetchzip }:
fetchzip {
  url = "https://github.com/NixOS/patchelf/releases/download/0.18.0/patchelf-0.18.0.tar.gz";
  hash = "sha256-3ABYlME9R8klcpJ7MQpyFEFwHmxDDEzIYBqu/CpDYmg=";
}

This archive has all its contents in a directory named patchelf-0.18.0. This means that after decompressing, you’d have to enter this directory to see the contents of the archive. However, fetchzip makes this easier through the attribute stripRoot (enabled by default).

After building the recipe, the derivation output will show all the files in the archive at the top level:

$ nix-build
(output removed for clarity)
/nix/store/1b7h3fvmgrcddvs0m299hnqxlgli1yjw-source

$ ls /nix/store/1b7h3fvmgrcddvs0m299hnqxlgli1yjw-source
aclocal.m4  completions  configure.ac  m4           Makefile.in  patchelf.spec     README.md  tests
build-aux   configure    COPYING       Makefile.am  patchelf.1   patchelf.spec.in  src        version

If stripRoot is set to false, the derivation output will be the decompressed archive as-is:

{ fetchzip }:
fetchzip {
  url = "https://github.com/NixOS/patchelf/releases/download/0.18.0/patchelf-0.18.0.tar.gz";
  hash = "sha256-uv3FuKE4DqpHT3yfE0qcnq0gYjDNQNKZEZt2+PUAneg=";
  stripRoot = false;
}

Caution

The hash changed! Whenever changing attributes of a Nixpkgs fetcher, remember to invalidate the hash, otherwise you won’t get the results you’re expecting!

After building the recipe:

$ nix-build
(output removed for clarity)
/nix/store/2hy5bxw7xgbgxkn0i4x6hjr8w3dbx16c-source

$ ls /nix/store/2hy5bxw7xgbgxkn0i4x6hjr8w3dbx16c-source
patchelf-0.18.0

Example 310. Using fetchzip to decompress a .rar file

The unrar package provides a setup hook to decompress .rar archives during the unpack phase, which can be used with fetchzip to decompress those archives:

{ fetchzip, unrar }:
fetchzip {
  url = "https://archive.org/download/SpaceCadet_Plus95/Space_Cadet.rar";
  hash = "sha256-fC+zsR8BY6vXpUkVd6i1jF0IZZxVKVvNi6VWCKT+pA4=";
  stripRoot = false;
  nativeBuildInputs = [ unrar ];
}

Since this particular .rar file doesn’t put its contents in a directory inside the archive, stripRoot must be set to false.

After building the recipe, the derivation output will show the decompressed files:

$ nix-build
(output removed for clarity)
/nix/store/zpn7knxfva6rfjja2gbb4p3l9w1f0d36-source

$ ls /nix/store/zpn7knxfva6rfjja2gbb4p3l9w1f0d36-source
FONT.DAT      PINBALL.DAT  PINBALL.EXE	PINBALL2.MID  TABLE.BMP    WMCONFIG.EXE
MSCREATE.DIR  PINBALL.DOC  PINBALL.MID	Sounds	     WAVEMIX.INF

fetchpatch

fetchpatch works very similarly to fetchurl with the same arguments expected. It expects patch files as a source and performs normalization on them before computing the checksum. For example, it will remove comments or other unstable parts that are sometimes added by version control systems and can change over time.

  • relative: Similar to using git-diff’s --relative flag, only keep changes inside the specified directory, making paths relative to it.

  • stripLen: Remove the first stripLen components of pathnames in the patch.

  • decode: Pipe the downloaded data through this command before processing it as a patch.

  • extraPrefix: Prefix pathnames by this string.

  • excludes: Exclude files matching these patterns (applies after the above arguments).

  • includes: Include only files matching these patterns (applies after the above arguments).

  • hunks: Choose the specified hunks from each file (applies after the above arguments). Note that you can specify a list of numbers or ranges of numbers (for example, [ 1 2 3 4 ], [ "1-4" ], [ "-4" ], or [ "1-" ] would all be the same effective range in a patch applying 4 hunks to a single file).

  • revert: Revert the patch.

Note that because the checksum is computed after applying these effects, using or modifying these arguments will have no effect unless the hash argument is changed as well.

Most other fetchers return a directory rather than a single file.

fetchDebianPatch

A wrapper around fetchpatch, which takes:

  • patch and hash: the patch’s filename, and its hash after normalization by fetchpatch ;

  • pname: the Debian source package’s name ;

  • version: the upstream version number ;

  • debianRevision: the Debian revision number if applicable ;

  • the area of the Debian archive: main (default), contrib, or non-free.

Here is an example of fetchDebianPatch in action:

{
  lib,
  fetchDebianPatch,
  buildPythonPackage,
}:

buildPythonPackage rec {
  pname = "pysimplesoap";
  version = "1.16.2";
  src = <...>;

  patches = [
    (fetchDebianPatch {
      inherit pname version;
      debianRevision = "5";
      patch = "Add-quotes-to-SOAPAction-header-in-SoapClient.patch";
      hash = "sha256-xA8Wnrpr31H8wy3zHSNfezFNjUJt1HbSXn3qUMzeKc0=";
    })
  ];

  # ...
}

Patches are fetched from sources.debian.org, and so must come from a package version that was uploaded to the Debian archive. Packages may be removed from there once that specific version isn’t in any suite anymore (stable, testing, unstable, etc.), so maintainers should use copy-tarballs.pl to archive the patch if it needs to be available longer-term.

fetchsvn

Used with Subversion. Expects url to a Subversion directory, rev, and hash.

fetchgit

Used with Git. Expects url to a Git repo, rev or tag, and hash. rev in this case can be the full git commit id (SHA1 hash), or use tag for a tag name like refs/tags/v1.0.

If you want to fetch a tag you should pass the tag parameter instead of rev which has the same effect as setting rev = "refs/tags"/${version}". This is safer than just setting rev = version w.r.t. possible branch and tag name conflicts.

Additionally, the following optional arguments can be given:

fetchSubmodules (Boolean)

Whether to also fetch the submodules of a repository.

fetchLFS (Boolean)

Whether to fetch LFS objects.

preFetch (String)

Shell code to be executed before the repository has been fetched, to allow changing the environment the fetcher runs in.

postFetch (String)

Shell code executed after the repository has been fetched successfully. This can do things like check or transform the file.

leaveDotGit (Boolean)

Whether the .git directory of the clone should not be removed after checkout.

Be warned though that the git repository format is not stable and this flag is therefore not suitable for actual use by itself. Only use this for testing purposes or in conjunction with removing the .git directory in postFetch.

deepClone (Boolean)

Clone the entire repository as opposed to just creating a shallow clone. This implies leaveDotGit.

fetchTags (Boolean)

Whether to fetch all tags from the remote repository. This is useful when the build process needs to run git describe or other commands that require tag information to be available. This parameter implies leaveDotGit, as tags are stored in the .git directory.

sparseCheckout (List of String)

Prevent git from fetching unnecessary blobs from server. This is useful if only parts of the repository are needed.

Example 311. Use sparseCheckout to only include some directories:
{ stdenv, fetchgit }:

stdenv.mkDerivation {
  name = "hello";
  src = fetchgit {
    url = "https://...";
    sparseCheckout = [
      "directory/to/be/included"
      "another/directory"
    ];
    hash = "sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=";
  };
}

See git sparse-checkout for more information.

rootDir (String)

When not empty, copy only contents of the subdirectory of the repository to the result. Automatically sets sparseCheckout and nonConeMode to avoid checking out any extra pieces. Incompatible with leaveDotGit.

Some additional parameters for niche use-cases can be found listed in the function parameters in the declaration of fetchgit: pkgs/build-support/fetchgit/default.nix. Future parameters additions might also happen without immediately being documented here.

fetchfossil

Used with Fossil. Expects url to a Fossil archive, rev, and hash.

fetchcvs

Used with CVS. Expects cvsRoot, tag, and hash.

fetchhg

Used with Mercurial. Expects url, rev, hash, overridable with <pkg>.overrideAttrs.

A number of fetcher functions wrap part of fetchurl and fetchzip. They are mainly convenience functions intended for commonly used destinations of source code in Nixpkgs. These wrapper fetchers are listed below.

fetchFromGitea, fetchFromForgejo and fetchFromCodeberg

fetchFromGitea, also aliased to fetchFromForgejo, expects five arguments. domain is the Gitea/Forgejo server name. owner is a string corresponding to the user or organization that controls this repository. repo corresponds to the name of the software repository. These are located at the top of every Gitea/Forgejo HTML page as owner/repo. rev corresponds to the Git commit hash or tag (e.g v1.0) that will be downloaded from Git. Finally, hash corresponds to the hash of the extracted directory. Again, other hash algorithms are also available but hash is currently preferred.

As <codeberg.org> is currently the most popular public Forgejo server, the fetchFromCodeberg fetcher is also available, which pre-fills the domain attribute.

fetchFromGitHub

fetchFromGitHub expects four arguments. owner is a string corresponding to the GitHub user or organization that controls this repository. repo corresponds to the name of the software repository. These are located at the top of every GitHub HTML page as owner/repo. rev corresponds to the Git commit hash or tag (e.g v1.0) that will be downloaded from Git. If you need to fetch a tag however, you should prefer to use the tag parameter which achieves this in a safer way with less boilerplate. Finally, hash corresponds to the hash of the extracted directory. Again, other hash algorithms are also available, but hash is currently preferred.

To use a different GitHub instance, use githubBase (defaults to "github.com").

By default, fetchFromGitHub uses fetchzip to download GitHub’s source archive for the specified revision. However, fetchFromGitHub will automatically switch to using fetchgit in any of these cases:

  • forceFetchGit, leaveDotGit, deepClone, fetchLFS, or fetchSubmodules are set to true

  • sparseCheckout contains any entries (is a non-empty list)

  • rootDir is set to a non-empty string

When fetchgit is used, refer to the fetchgit section for documentation of its available options.

fetchFromGitLab

This is used with GitLab repositories. It behaves similarly to fetchFromGitHub, and expects owner, repo, rev, and hash.

To use a specific GitLab instance, use domain (defaults to "gitlab.com").

fetchFromGitiles

This is used with Gitiles repositories. The arguments expected are similar to fetchgit.

fetchFromBitbucket

Used for repositories hosted on Bitbucket ("bitbucket.org") owned by the Australian-based Atlassian Corporation. It requires an owner and repo argument which are both strings that reference the workspace ID and repository name hosted on Bitbucket cloud as well as either a tag or rev argument.

By default, fetchFromBitbucket will attempt to download a commit snapshot tarball at the specified tag or rev at https://bitbucket.org/<owner>/<repo>/get/<tag-or-rev>.tar.gz

However, fetchFromBitbucket will automatically switch to using fetchgit and fetch from https://bitbucket.org/<owner>/<repo>.git in any of these cases:

  • forceFetchGit, leaveDotGit, deepClone, fetchLFS, or fetchSubmodules are set to true

  • sparseCheckout contains any entries (is a non-empty list)

  • rootDir is set to a non-empty string

When fetchgit is used, refer to the fetchgit section for documentation of its available options.

fetchFromRepoOrCz

This is used with repo.or.cz repositories. The arguments expected are very similar to fetchFromGitHub above.

fetchFromSourcehut

This is used with sourcehut repositories. Similar to fetchFromGitHub above, it expects owner, repo, rev and hash, but don’t forget the tilde (~) in front of the username! Expected arguments also include vc (“git” (default) or “hg”), domain and fetchSubmodules.

If fetchSubmodules is true, fetchFromSourcehut uses fetchgit or fetchhg with fetchSubmodules or fetchSubrepos set to true, respectively. Otherwise, the fetcher uses fetchzip.

fetchFromRadicle

This is used with Radicle repositories. The arguments expected are similar to fetchgit.

Requires a seed argument (e.g. seed.radicle.dev or rosa.radicle.network) and a repo argument (the repository id without the rad: prefix). Also accepts an optional node argument which contains the id of the node from which to fetch the specified ref. If node is null (the default), a canonical ref is fetched instead.

fetchFromRadicle {
  seed = "seed.radicle.dev";
  repo = "z3gqcJUoA1n9HaHKufZs5FCSGazv5"; # heartwood
  tag = "releases/1.3.0";
  hash = "sha256-4o88BWKGGOjCIQy7anvzbA/kPOO+ZsLMzXJhE61odjw=";
}

fetchRadiclePatch

fetchRadiclePatch works very similarly to fetchFromRadicle with almost the same arguments expected. However, instead of a rev or tag argument, a revision argument is expected, which contains the full revision id of the Radicle patch to fetch.

fetchRadiclePatch {
  seed = "rosa.radicle.network";
  repo = "z4V1sjrXqjvFdnCUbxPFqd5p4DtH5"; # radicle-explorer
  revision = "d97d872386c70607beda2fb3fc2e60449e0f4ce4"; # patch: d77e064
  hash = "sha256-ttnNqj0lhlSP6BGzEhhUOejKkkPruM9yMwA5p9Di4bk=";
}

requireFile

requireFile allows requesting files that cannot be fetched automatically, but whose content is known. This is a useful last-resort workaround for license restrictions that prohibit redistribution, or for downloads that are only accessible after authenticating interactively in a browser. If the requested file is present in the Nix store, the resulting derivation will not be built, because its expected output is already available. Otherwise, the builder will run, but fail with a message explaining to the user how to provide the file. The following code, for example:

requireFile {
  name = "jdk-${version}_linux-x64_bin.tar.gz";
  url = "https://www.oracle.com/java/technologies/javase-jdk11-downloads.html";
  hash = "sha256-lL00+F7jjT71nlKJ7HRQuUQ7kkxVYlZh//5msD8sjeI=";
}

results in this error message:

***
Unfortunately, we cannot download file jdk-11.0.10_linux-x64_bin.tar.gz automatically.
Please go to https://www.oracle.com/java/technologies/javase-jdk11-downloads.html to download it yourself, and add it to the Nix store
using either
  nix-store --add-fixed sha256 jdk-11.0.10_linux-x64_bin.tar.gz
or
  nix-prefetch-url --type sha256 file:///path/to/jdk-11.0.10_linux-x64_bin.tar.gz

***

This function should only be used by non-redistributable software with an unfree license that we need to require the user to download manually. It produces packages that cannot be built automatically.

fetchtorrent

fetchtorrent expects two arguments. url which can either be a Magnet URI (Magnet Link) such as magnet:?xt=urn:btih:dd8255ecdc7ca55fb0bbf81323d87062db1f6d1c or an HTTP URL pointing to a .torrent file. It can also take a config argument which will craft a settings.json configuration file and give it to transmission, the underlying program that is performing the fetch. The available config options for transmission can be found here

{ fetchtorrent }:

fetchtorrent {
  config = {
    peer-limit-global = 100;
  };
  url = "magnet:?xt=urn:btih:dd8255ecdc7ca55fb0bbf81323d87062db1f6d1c";
  hash = "";
}

Parameters

  • url: Magnet URI (Magnet Link) such as magnet:?xt=urn:btih:dd8255ecdc7ca55fb0bbf81323d87062db1f6d1c or an HTTP URL pointing to a .torrent file.

  • backend: Which bittorrent program to use. Default: "transmission". Valid values are "rqbit" or "transmission". These are the two most suitable torrent clients for fetching in a fixed-output derivation at the time of writing, as they can be easily exited after usage. rqbit is written in Rust and has a smaller closure size than transmission, and the performance and peer discovery properties differs between these clients, requiring experimentation to decide upon which is the best.

  • config: When using transmission as the backend, a json configuration can be supplied to transmission. Refer to the upstream documentation for information on how to configure.

fetchItchIo

fetchItchIo is a fetcher for downloading game assets from itch.io. It accepts these arguments:

  • gameUrl: The store page URL of the game.

  • upload: The numerical ID of the asset to download. To find the upload ID of an asset, check the basename of the request URL when you download the asset using a browser.

  • hash.

  • name (optional): The derivation name, often the filename of the asset.

  • extraMessage (optional): Extra message printed if the API key is not provided or if the account did not purchase the game.

For this fetcher to work, the environment variable NIX_ITCHIO_API_KEY must be set for the nix building process (which is nix-daemon in multi-user mode), and it must belong to an account that has bought the game if it is behind a paywall. To get your API key, go to the “API key” section of your account settings on itch.io.

{ fetchItchIo }:

fetchItchIo {
  name = "DungeonDuelMonsters-linux-x64.zip";
  hash = "sha256-gq2nGwpaStqaVI1pL63xygxOI/z53o+zLwiKizG98Ks=";
  gameUrl = "https://mikaygo.itch.io/ddm";
  upload = "13371354";
}

Trivial build helpers

Nixpkgs provides a variety of wrapper functions that help build commonly useful derivations. Like stdenv.mkDerivation, each of these build helpers creates a derivation, but the arguments passed are different (usually simpler) from those required by stdenv.mkDerivation.

runCommandWith

The function runCommandWith returns a derivation built using the specified command(s), in a specified environment.

It is the underlying base function of all runCommand* variants. The general behavior is controlled via a single attribute set passed as the first argument, and allows specifying stdenv freely.

The following runCommand* variants exist: runCommand, runCommandCC, and runCommandLocal.

Type

runCommandWith :: {
  name :: name;
  stdenv? :: Derivation;
  runLocal? :: Bool;
  derivationArgs? :: { ... };
} -> String -> Derivation

Inputs

name (String)

The derivation’s name, which Nix will append to the store path; see mkDerivation.

runLocal (Boolean)

If set to true this forces the derivation to be built locally, not using substitutes nor remote builds. This is intended for very cheap commands (<1s execution time) which can be sped up by avoiding the network round-trip(s). Its effect is to set preferLocalBuild = true and allowSubstitutes = false.

Note

This prevents the use of substituters, so only set runLocal (or use runCommandLocal) when certain the user will always have a builder for the system of the derivation. This should be true for most trivial use cases (e.g., just copying some files to a different location or adding symlinks) because there the system is usually the same as builtins.currentSystem.

stdenv (Derivation)

The standard environment to use, defaulting to pkgs.stdenv.

derivationArgs (Attribute set)

Additional arguments for mkDerivation.

buildCommand (String)

Shell commands to run in the derivation builder.

Note

You have to create a file or directory $out for Nix to be able to run the builder successfully.

Example 312. Invocation of runCommandWith
runCommandWith
  {
    name = "example";
    derivationArgs.nativeBuildInputs = [ cowsay ];
  }
  ''
    cowsay > $out <<EOMOO
    'runCommandWith' is a bit cumbersome,
    so we have more ergonomic wrappers.
    EOMOO
  ''

runCommand and runCommandCC

The function runCommand returns a derivation built using the specified command(s), in the stdenvNoCC environment.

runCommandCC is similar but uses the default compiler environment. To minimize dependencies, runCommandCC should only be used when the build command needs a C compiler.

runCommandLocal is also similar to runCommand, but forces the derivation to be built locally. See the note on runCommandWith about runLocal.

Type

runCommand      :: String -> AttrSet -> String -> Derivation
runCommandCC    :: String -> AttrSet -> String -> Derivation
runCommandLocal :: String -> AttrSet -> String -> Derivation

Input

While the type signature(s) differ from runCommandWith, individual arguments with the same name will have the same type and meaning:

name (String)

The derivation’s name

derivationArgs (Attribute set)

Additional parameters passed to [mkDerivation]

buildCommand (String)

The command(s) run to build the derivation.

Example 313. Invocation of runCommand
runCommand "my-example" { } ''
  echo My example command is running

  mkdir $out

  echo I can write data to the Nix store > $out/message

  echo I can also run basic commands like:

  echo ls
  ls

  echo whoami
  whoami

  echo date
  date
''

Note

runCommand name derivationArgs buildCommand is equivalent to

runCommandWith {
  inherit name derivationArgs;
  stdenv = stdenvNoCC;
} buildCommand

Likewise, runCommandCC name derivationArgs buildCommand is equivalent to

runCommandWith { inherit name derivationArgs; } buildCommand

Writing text files

Nixpkgs provides the following functions for producing derivations which write text files or executable scripts into the Nix store. They are useful for creating files from Nix expressions, and are all implemented as convenience wrappers around writeTextFile.

Each of these functions will cause a derivation to be produced. When you coerce the result of each of these functions to a string with string interpolation or toString, it will evaluate to the store path of this derivation.

Note

Some of these functions will put the resulting files within a directory inside the derivation output. If you need to refer to the resulting files somewhere else in a Nix expression, append their path to the derivation’s store path.

For example, if the file destination is a directory:

{
  my-file = writeTextFile {
    name = "my-file";
    text = ''
      Contents of File
    '';
    destination = "/share/my-file";
  };
}

Remember to append “/share/my-file” to the resulting store path when using it elsewhere:

writeShellScript "evaluate-my-file.sh" ''
  cat ${my-file}/share/my-file
''

makeDesktopItem

Write an XDG desktop file to the Nix store.

This function is usually used to add desktop items to a package through the copyDesktopItems hook.

makeDesktopItem adheres to version 1.4 of the specification.

Inputs

makeDesktopItem takes an attribute set that accepts most values from the XDG specification.

All recognised keys from the specification are supported with the exception of the “Hidden” field. The keys are converted into camelCase format, but correspond 1:1 to their equivalent in the specification: genericName, noDisplay, comment, icon, onlyShowIn, notShowIn, dbusActivatable, tryExec, exec, path, terminal, mimeTypes, categories, implements, keywords, startupNotify, startupWMClass, url, prefersNonDefaultGPU.

The “Version” field is hardcoded to the version makeDesktopItem currently adheres to.

The following fields are either required, are of a different type than in the specification, carry specific default values, or are additional fields supported by makeDesktopItem:

name (String)

The name of the desktop file in the Nix store.

type (String; optional)

Default value: "Application"

desktopName (String)

Corresponds to the “Name” field of the specification.

actions (List of Attribute set; optional)

A list of attribute sets {name, exec?, icon?}

extraConfig (Attribute set; optional)

Additional key/value pairs to be added verbatim to the desktop file. Attributes need to be prefixed with ‘X-’.

Examples

Example 314. Usage 1 of makeDesktopItem

Write a desktop file /nix/store/<store path>/my-program.desktop to the Nix store.

{ makeDesktopItem }:
makeDesktopItem {
  name = "my-program";
  desktopName = "My Program";
  genericName = "Video Player";
  noDisplay = false;
  comment = "Cool video player";
  icon = "/path/to/icon";
  onlyShowIn = [ "KDE" ];
  dbusActivatable = true;
  tryExec = "my-program";
  exec = "my-program --someflag";
  path = "/some/working/path";
  terminal = false;
  actions.example = {
    name = "New Window";
    exec = "my-program --new-window";
    icon = "/some/icon";
  };
  mimeTypes = [ "video/mp4" ];
  categories = [ "Utility" ];
  implements = [ "org.my-program" ];
  keywords = [
    "Video"
    "Player"
  ];
  startupNotify = false;
  startupWMClass = "MyProgram";
  prefersNonDefaultGPU = false;
  extraConfig.X-SomeExtension = "somevalue";
}

Example 315. Usage 2 of makeDesktopItem

Override the hello package to add a desktop item.

{
  copyDesktopItems,
  hello,
  makeDesktopItem,
}:

hello.overrideAttrs {
  nativeBuildInputs = [ copyDesktopItems ];

  desktopItems = [
    (makeDesktopItem {
      name = "hello";
      desktopName = "Hello";
      exec = "hello";
    })
  ];
}

writeTextFile

Write a text file to the Nix store.

writeTextFile takes an attribute set with the following possible attributes:

name (String)

Corresponds to the name used in the Nix store path identifier.

text (String)

The contents of the file.

executable (Bool, optional)

Make this file have the executable bit set.

Default: false

destination (String, optional)

A subpath under the derivation’s output path into which to put the file. Subdirectories are created automatically when the derivation is realised.

By default, the store path itself will be a file containing the text contents.

Default: ""

checkPhase (String, optional)

Commands to run after generating the file.

Default: ""

meta (Attribute set, optional)

Additional metadata for the derivation.

Default: {}

allowSubstitutes (Bool, optional)

Whether to allow substituting from a binary cache. Passed through to allowSubstitutes of the underlying call to derivation.

It defaults to false, as running the derivation’s simple builder executable locally is assumed to be faster than network operations. Set it to true if the checkPhase step is expensive.

Default: false

preferLocalBuild (Bool, optional)

Whether to prefer building locally, even if faster remote build machines are available.

Passed through to preferLocalBuild of the underlying call to derivation.

It defaults to true for the same reason allowSubstitutes defaults to false.

Default: true

derivationArgs (Attribute set, optional)

Extra arguments to pass to the underlying call to stdenv.mkDerivation.

Default: {}

The resulting store path will include some variation of the name, and it will be a file unless destination is used, in which case it will be a directory.

Example 316. Usage 1 of writeTextFile

Write my-file to /nix/store/<store path>/some/subpath/my-cool-script, making it executable. Also run a check on the resulting file in a checkPhase, and supply values for the less-used options.

writeTextFile {
  name = "my-cool-script";
  text = ''
    #!/bin/sh
    echo "This is my cool script!"
  '';
  executable = true;
  destination = "/some/subpath/my-cool-script";
  checkPhase = ''
    ${pkgs.shellcheck}/bin/shellcheck $out/some/subpath/my-cool-script
  '';
  meta = {
    license = pkgs.lib.licenses.cc0;
  };
  allowSubstitutes = true;
  preferLocalBuild = false;
}

Example 317. Usage 2 of writeTextFile

Write the string Contents of File to /nix/store/<store path>. See also the the section called “writeText helper function.

writeTextFile {
  name = "my-file";
  text = ''
    Contents of File
  '';
}

Example 318. Usage 3 of writeTextFile

Write an executable script my-script to /nix/store/<store path>/bin/my-script. See also the the section called “writeScriptBin helper function.

writeTextFile {
  name = "my-script";
  text = ''
    echo "hi"
  '';
  executable = true;
  destination = "/bin/my-script";
}

writeText

Write a text file to the Nix store

writeText takes the following arguments: a string.

name (String)

The name used in the Nix store path.

text (String)

The contents of the file.

The store path will include the name, and it will be a file.

Example 319. Usage of writeText

Write the string Contents of File to /nix/store/<store path>:

writeText "my-file" ''
  Contents of File
''

This is equivalent to:

writeTextFile {
  name = "my-file";
  text = ''
    Contents of File
  '';
}

writeTextDir

Write a text file within a subdirectory of the Nix store.

writeTextDir takes the following arguments:

path (String)

The destination within the Nix store path under which to create the file.

text (String)

The contents of the file.

The store path will be a directory.

Example 320. Usage of writeTextDir

Write the string Contents of File to /nix/store/<store path>/share/my-file:

writeTextDir "share/my-file" ''
  Contents of File
''

This is equivalent to:

writeTextFile {
  name = "my-file";
  text = ''
    Contents of File
  '';
  destination = "/share/my-file";
}

writeScript

Write an executable script file to the Nix store.

writeScript takes the following arguments:

name (String)

The name used in the Nix store path.

text (String)

The contents of the file.

The created file is marked as executable. The store path will include the name, and it will be a file.

Example 321. Usage of writeScript

Write the string Contents of File to /nix/store/<store path> and make the file executable.

writeScript "my-file" ''
  Contents of File
''

This is equivalent to:

writeTextFile {
  name = "my-file";
  text = ''
    Contents of File
  '';
  executable = true;
}

writeScriptBin

Write a script within a bin subdirectory of a directory in the Nix store. This is for consistency with the convention of software packages placing executables under bin.

writeScriptBin takes the following arguments:

name (String)

The name used in the Nix store path and within the file created under the store path.

text (String)

The contents of the file.

The created file is marked as executable. The file’s contents will be put into /nix/store/<store path>/bin/<name>. The store path will include the name, and it will be a directory.

Example 322. Usage of writeScriptBin
writeScriptBin "my-script" ''
  echo "hi"
''

This is equivalent to:

writeTextFile {
  name = "my-script";
  text = ''
    echo "hi"
  '';
  executable = true;
  destination = "/bin/my-script";
}

writeShellScript

Write a Bash script to the store.

writeShellScript takes the following arguments:

name (String)

The name used in the Nix store path.

text (String)

The contents of the file.

The created file is marked as executable. The store path will include the name, and it will be a file.

This function is almost exactly like the section called “writeScript, except that it prepends to the file a shebang line that points to the version of Bash used in Nixpkgs.

Example 323. Usage of writeShellScript
writeShellScript "my-script" ''
  echo "hi"
''

This is equivalent to:

writeTextFile {
  name = "my-script";
  text = ''
    #! ${pkgs.runtimeShell}
    echo "hi"
  '';
  executable = true;
}

writeShellScriptBin

Write a Bash script to a “bin” subdirectory of a directory in the Nix store.

writeShellScriptBin takes the following arguments:

name (String)

The name used in the Nix store path and within the file generated under the store path.

text (String)

The contents of the file.

The file’s contents will be put into /nix/store/<store path>/bin/<name>. The store path will include the name, and it will be a directory.

This function is a combination of the section called “writeShellScript and the section called “writeScriptBin.

Example 324. Usage of writeShellScriptBin
writeShellScriptBin "my-script" ''
  echo "hi"
''

This is equivalent to:

writeTextFile {
  name = "my-script";
  text = ''
    #! ${pkgs.runtimeShell}
    echo "hi"
  '';
  executable = true;
  destination = "/bin/my-script";
}

concatTextFile, concatText, concatScript

These functions concatenate files to the Nix store in a single file. This is useful for configuration files structured in lines of text. concatTextFile takes an attribute set and expects two arguments, name and files. name corresponds to the name used in the Nix store path. files will be the files to be concatenated. You can also set executable to true to make this file have the executable bit set. concatText and concatScript are simple wrappers over concatTextFile.

Here are a few examples:

# Writes my-file to /nix/store/<store path>
concatTextFile
  {
    name = "my-file";
    files = [
      drv1
      "${drv2}/path/to/file"
    ];
  }
  # See also the `concatText` helper function below.

  # Writes executable my-file to /nix/store/<store path>/bin/my-file
  concatTextFile
  {
    name = "my-file";
    files = [
      drv1
      "${drv2}/path/to/file"
    ];
    executable = true;
    destination = "/bin/my-file";
  }
  # Writes contents of files to /nix/store/<store path>
  concatText
  "my-file"
  [
    file1
    file2
  ]

  # Writes contents of files to /nix/store/<store path>
  concatScript
  "my-file"
  [
    file1
    file2
  ]

writeShellApplication

writeShellApplication is similar to writeShellScriptBin and writeScriptBin but supports runtime dependencies with runtimeInputs. Writes an executable shell script to /nix/store/<store path>/bin/<name> and checks its syntax with shellcheck and the bash’s -n option. Some basic Bash options are set by default (errexit, nounset, and pipefail), but can be overridden with bashOptions.

Extra arguments may be passed to stdenv.mkDerivation by setting derivationArgs; note that variables set in this manner will be set when the shell script is built, not when it’s run. Runtime environment variables can be set with the runtimeEnv argument.

writeShellApplication has the following arguments:

name (String)

The name of the script to write.

text (String)

The shell script’s text, not including a shebang.

runtimeInputs (List of derivations or strings, optional)

Inputs to add to the shell script’s $PATH at runtime.

Each elements can either be a normal derivation, or a string containing a path, in which case it will be suffixed with /bin to create a PATH expression (see lib.strings.makeBinPath for more information).

runtimeEnv (Attribute set, optional)

Extra environment variables to set at runtime.

checkPhase (String, optional)

The checkPhase to run.

The script path will be given as $target in the checkPhase

Default behavior: run shellcheck (on supported platforms) and bash -n (check syntax but don’t execute commands).

excludeShellChecks (List of strings, optional)

Checks to exclude when running shellcheck.

For example, excludeShellChecks = [ "SC2016" ] would prevent shellcheck from reporting SC2016, but would still detect any other problems.

See the shellcheck wiki for a list of checks.

extraShellCheckFlags (List of strings, optional)

Extra command-line flags to pass to shellcheck.

bashOptions (List of strings, optional)

Bash options to activate with set -o at the start of the script

Default: [ "errexit" "nounset" "pipefail" ], which means:

  1. A failing command inside of a command list or pipeline will make the script exit, except if used as a conditional (inside a while, if, &&, ||, etc.);

  2. Any attempt to expand an undefined variable will make the script exit.

inheritPath (Bool, optional)

Whether the script will inherit the PATH from its parent environment.

Default: true

meta (Attribute set, optional)

stdenv.mkDerivation’s meta argument

passthru (Attribute set, optional)

stdenv.mkDerivation’s passthru argument

derivationArgs (Attribute set, optional)

Extra arguments to pass to stdenv.mkDerivation

Caution

Certain derivation attributes are also set internally, so overriding those could cause problems.

Example 325. Usage of writeShellApplication

The following shell application can refer to curl directly, rather than needing to write ${curl}/bin/curl

writeShellApplication {
  name = "show-nixos-org";

  runtimeInputs = [
    curl
    w3m
  ];

  text = ''
    curl -s 'https://nixos.org' | w3m -dump -T text/html
  '';
}

symlinkJoin

This can be used to put many derivations into the same directory structure. It works by creating a new derivation and adding symlinks to each of the paths listed. It expects two arguments, name, and paths. name (or alternatively pname and version) is the name used in the Nix store path for the created derivation. paths is a list of paths that will be symlinked. These paths can be to Nix store derivations or any other subdirectory contained within. Here is an example:

# adds symlinks of hello and stack to current build and prints "links added"
symlinkJoin {
  name = "myexample";
  paths = [
    pkgs.hello
    pkgs.stack
  ];
  postBuild = "echo links added";
}

This creates a derivation with a directory structure like the following:

/nix/store/sglsr5g079a5235hy29da3mq3hv8sjmm-myexample
|-- bin
|   |-- hello -> /nix/store/qy93dp4a3rqyn2mz63fbxjg228hffwyw-hello-2.10/bin/hello
|   `-- stack -> /nix/store/6lzdpxshx78281vy056lbk553ijsdr44-stack-2.1.3.1/bin/stack
`-- share
    |-- bash-completion
    |   `-- completions
    |       `-- stack -> /nix/store/6lzdpxshx78281vy056lbk553ijsdr44-stack-2.1.3.1/share/bash-completion/completions/stack
    |-- fish
    |   `-- vendor_completions.d
    |       `-- stack.fish -> /nix/store/6lzdpxshx78281vy056lbk553ijsdr44-stack-2.1.3.1/share/fish/vendor_completions.d/stack.fish
...

writeClosure

Given a list of store paths (or string-like expressions coercible to store paths), write their collective closure to a text file.

The result is equivalent to the output of nix-store -q --requisites.

For example,

writeClosure [ (writeScriptBin "hi" "${hello}/bin/hello") ]

produces an output path /nix/store/<hash>-runtime-deps containing

/nix/store/<hash>-hello-2.10
/nix/store/<hash>-hi
/nix/store/<hash>-libidn2-2.3.0
/nix/store/<hash>-libunistring-0.9.10
/nix/store/<hash>-glibc-2.32-40

You can see that this includes hi, the original input path, hello, which is a direct reference, but also the other paths that are indirectly required to run hello.

writeDirectReferencesToFile

Writes the set of references to the output file, that is, their immediate dependencies.

This produces the equivalent of nix-store -q --references.

For example,

writeDirectReferencesToFile (writeScriptBin "hi" "${hello}/bin/hello")

produces an output path /nix/store/<hash>-runtime-references containing

/nix/store/<hash>-hello-2.10

but none of hello’s dependencies because those are not referenced directly by hi’s output.

Testers

This chapter describes several testing builders which are available in the testers namespace.

hasPkgConfigModules

Checks whether a package exposes a given list of pkg-config modules. If the moduleNames argument is omitted, hasPkgConfigModules will use meta.pkgConfigModules.

Example 326. Check that pkg-config modules are exposed using default values
{
  passthru.tests.pkg-config = testers.hasPkgConfigModules { package = finalAttrs.finalPackage; };

  meta.pkgConfigModules = [ "libfoo" ];
}

Example 327. Check that pkg-config modules are exposed using explicit module names
{
  passthru.tests.pkg-config = testers.hasPkgConfigModules {
    package = finalAttrs.finalPackage;
    moduleNames = [ "libfoo" ];
  };
}

hasCmakeConfigModules

Checks whether a package exposes a given list of *config.cmake modules. Note the moduleNames used in cmake find_package are case sensitive.

Example 328. Check that *config.cmake modules are exposed using explicit module names
{
  passthru.tests.cmake-config = testers.hasCmakeConfigModules {
    package = finalAttrs.finalPackage;
    moduleNames = [ "Foo" ];
  };
}

lycheeLinkCheck

Check a packaged static site’s links with the lychee package.

You may use Nix to reproducibly build static websites, such as for software documentation. Some packages will install documentation in their out or doc outputs, or maybe you have a dedicated package where you’ve made your static site reproducible by running a generator, such as Hugo or mdBook, in a derivation.

If you have a static site that can be built with Nix, you can use lycheeLinkCheck to check that the hyperlinks in your site are correct, and do so as part of your Nix workflow and CI.

Example 329. Check hyperlinks in the nix documentation
testers.lycheeLinkCheck { site = nix.doc + "/share/doc/nix/manual"; }

Return value

This tester produces a package that does not produce useful outputs, but only succeeds if the hyperlinks in your site are correct. The build log will list the broken links.

It has two modes:

  • Build the returned derivation; its build process will check that internal hyperlinks are correct. This runs in the sandbox, so it will not check external hyperlinks, but it is quick and reliable.

  • Invoke the .online attribute with nix run (experimental). This runs outside the sandbox, and checks that both internal and external hyperlinks are correct. Example:

    nix run nixpkgs#lychee.tests.ok.online
    

Inputs

site (path or derivation) {#tester-lycheeLinkCheck-param-site}

The path to the files to check.

remap (attribute set, optional) {#tester-lycheeLinkCheck-param-remap}

An attribute set where the attribute names are regular expressions. The values should be strings, derivations, or path values.

In the returned check’s default configuration, external URLs are only checked when you run the .online attribute.

By adding remappings, you can check offline that URLs to external resources are correct, by providing a stand-in from the file system.

Before checking the existence of a URL, the regular expressions are matched and replaced by their corresponding values.

Example:

{
  "https://nix\\.dev/manual/nix/[a-z0-9.-]*" = "${nix.doc}/share/doc/nix/manual";
  "https://nixos\\.org/manual/nix/(un)?stable" =
    "${emptyDirectory}/placeholder-to-disallow-old-nix-docs-urls";
}

Store paths in the attribute values are automatically prefixed with file://, because lychee requires this for paths in the file system. If this is a problem, or if you need to control the order in which replacements are performed, use extraConfig.remap instead.

extraConfig (attribute set) {#tester-lycheeLinkCheck-param-extraConfig}

Extra configuration to pass to lychee in its configuration file. It is automatically translated to TOML.

Example: { "include_verbatim" = true; }

extraArgs (list of strings, optional) {#tester-lycheeLinkCheck-param-extraArgs}

Extra command line arguments to pass to the lychee invocation. These are passed in both the offline (build) and online modes.

Example: [ "--format" "json" ]

lychee (derivation, optional) {#tester-lycheeLinkCheck-param-lychee}

The lychee package to use.

shellcheck

Run files through shellcheck, a static analysis tool for shell scripts, failing if there are any issues.

Example 330. Run testers.shellcheck

A single script

testers.shellcheck {
  name = "script";
  src = ./script.sh;
}

Multiple files

let
  inherit (lib) fileset;
in
testers.shellcheck {
  name = "nixbsd-activate";
  src = fileset.toSource {
    root = ./.;
    fileset = fileset.unions [
      ./lib.sh
      ./nixbsd-activate
    ];
  };
}

Inputs

name (string, optional)

The name of the test. name will be required at a future point because it massively improves traceability of test failures, but is kept optional for now to avoid breaking existing usages. Defaults to run-shellcheck. The name of the derivation produced by the tester is shellcheck-${name} when name is supplied.

src (path-like)

The path to the shell script(s) to check. This can be a single file or a directory containing shell files. All files in src will be checked, so you may want to provide fileset-based source instead of a whole directory.

Return value

A derivation that runs shellcheck on the given script(s), producing an empty output if no issues are found. The build will fail if shellcheck finds any issues.

shfmt

Run files through shfmt, a shell script formatter, failing if any files are reformatted.

Example 331. Run testers.shfmt

A single script

testers.shfmt {
  name = "script";
  src = ./script.sh;
}

Multiple files

let
  inherit (lib) fileset;
in
testers.shfmt {
  name = "nixbsd";
  src = fileset.toSource {
    root = ./.;
    fileset = fileset.unions [
      ./lib.sh
      ./nixbsd-activate
    ];
  };
}

Inputs

name (string)

The name of the test. name is required because it massively improves traceability of test failures. The name of the derivation produced by the tester is shfmt-${name}.

src (path-like)

The path to the shell script(s) to check. This can be a single file or a directory containing shell files. All files in src will be checked, so you may want to provide fileset-based source instead of a whole directory.

indent (integer, optional)

The number of spaces to use for indentation. Defaults to 2. A value of 0 indents with tabs.

Return value

A derivation that runs shfmt on the given script(s), producing an empty output upon success. The build will fail if shfmt reformats anything.

testVersion

Checks that the output from running a command contains the specified version string in it as a whole word.

NOTE: This is a check you add to passthru.tests which is mainly run by OfBorg, but not in Hydra. If you want a version check failure to block the build altogether, then versionCheckHook is the tool you’re looking for (and recommended for quick builds). The motivation for adding either of these checks would be:

  • Catch dynamic linking errors and such and missing environment variables that should be added by wrapping.

  • Probable protection against accidentally building the wrong version, for example when using an “old” hash in a fixed-output derivation.

By default, the command to be run will be inferred from the given package attribute: it will check meta.mainProgram first, and fall back to pname or name. The default argument to the command is --version, and the version to be checked will be inferred from the given package attribute as well.

Example 332. Check a program version using all the default values

This example will run the command hello --version, and then check that the version of the hello package is in the output of the command.

{ passthru.tests.version = testers.testVersion { package = hello; }; }

Example 333. Check the program version using a specified command and expected version string

This example will run the command leetcode -V, and then check that leetcode 0.4.2 is in the output of the command as a whole word (separated by whitespaces). This means that an output like “leetcode 0.4.21” would fail the tests, and an output like “You’re running leetcode 0.4.2” would pass the tests.

A common usage of the version attribute is to specify version = "v${version}".

{
  version = "0.4.2";

  passthru.tests.version = testers.testVersion {
    package = leetcode-cli;
    command = "leetcode -V";
    version = "leetcode ${version}";
  };
}

testBuildFailure

Make sure that a build does not succeed. This is useful for testing testers.

This returns a derivation with an override on the builder, with the following effects:

  • Fail the build when the original builder succeeds

  • Move $out to $out/result, if it exists (assuming out is the default output)

  • Save the build log to $out/testBuildFailure.log (same)

While testBuildFailure is designed to keep changes to the original builder’s environment to a minimum, some small changes are inevitable:

  • The file $TMPDIR/testBuildFailure.log is present. It should not be deleted.

  • stdout and stderr are a pipe instead of a tty. This could be improved.

  • One or two extra processes are present in the sandbox during the original builder’s execution.

  • The derivation and output hashes are different, but not unusual.

  • The derivation includes a dependency on buildPackages.bash and expect-failure.sh, which is built to include a transitive dependency on buildPackages.coreutils and possibly more. These are not added to PATH or any other environment variable, so they should be hard to observe.

Example 334. Check that a build fails, and verify the changes made during build
runCommand "example"
  {
    failed = testers.testBuildFailure (
      runCommand "fail" { } ''
        echo ok-ish >$out
        echo failing though
        exit 3
      ''
    );
  }
  ''
    grep -F 'ok-ish' $failed/result
    grep -F 'failing though' $failed/testBuildFailure.log
    [[ 3 = $(cat $failed/testBuildFailure.exit) ]]
    touch $out
  ''

testBuildFailure'

This tester wraps the functionality provided by testers.testBuildFailure to make writing checks easier by simplifying checking the exit code of the builder and asserting the existence of entries in the builder’s log. Additionally, users may specify a script containing additional checks, accessing the result of applying testers.testBuildFailure through the variable failed.

NOTE: This tester will produce an empty output and exit with success if none of the checks fail; there is no need to touch "$out" in script.

Example 335. Check that a build fails, and verify the changes made during build

Re-using the example from testers.testBuildFailure, we can see how common checks are made easier and remove the need for runCommand:

testers.testBuildFailure' {
  drv = runCommand "doc-example" { } ''
    echo ok-ish >"$out"
    echo failing though
    exit 3
  '';
  expectedBuilderExitCode = 3;
  expectedBuilderLogEntries = [ "failing though" ];
  script = ''
    grep --silent -F 'ok-ish' "$failed/result"
  '';
}

Inputs

drv (derivation)

The failing derivation to wrap with testBuildFailure.

name (string, optional)

The name of the test. When not provided, this value defaults to testBuildFailure-${(testers.testBuildFailure drv).name}.

expectedBuilderExitCode (integer, optional)

The expected exit code of the builder of drv. When not provided, this value defaults to 1.

expectedBuilderLogEntries (array of string-like values, optional)

A list of string-like values which must be found in the builder’s log by exact match. When not provided, this value defaults to [ ].

NOTE: Patterns and regular expressions are not supported.

script (string, optional)

A string containing additional checks to run. When not provided, this value defaults to "". The result of testers.testBuildFailure drv is available through the variable failed. As an example, the builder’s log is at "$failed/testBuildFailure.log".

Return value

The tester produces an empty output and only succeeds when the checks using expectedBuilderExitCode, expectedBuilderLogEntries, and script succeed.

testEqualContents

Check that two paths have the same contents.

assertion (string)

A message that is printed before the comparison, after Checking:.

expected (path or value coercible to store path)

The path to the expected file system object content

actual (value coercible to store path)

The path to the actual file system object content to check

postFailureMessage (string)

A message that is printed last if the file system object contents at the two paths don’t match exactly.

checkMetadata (boolean)

Whether to fail on metadata differences, such as permissions or ownership. Defaults to true.

Example 336. Check that two paths have the same contents
testers.testEqualContents {
  assertion = "sed -e performs replacement";
  expected = writeText "expected" ''
    foo baz baz
  '';
  actual =
    runCommand "actual"
      {
        # not really necessary for a package that's in stdenv
        nativeBuildInputs = [ gnused ];
        base = writeText "base" ''
          foo bar baz
        '';
      }
      ''
        sed -e 's/bar/baz/g' $base >$out
      '';
  # if applicable
  postFailureMessage = ''
    The bar-baz replacer produced an unexpected result.
    If the new behavior is acceptable and validated against the bar-baz specification, run ./adopt-new-bar-baz-result.sh to adjust this test and require the new behavior.
  '';
}

testEqualArrayOrMap

Check that bash arrays (including associative arrays, referred to as “maps”) are populated correctly.

This can be used to ensure setup hooks are registered in a certain order, or to write unit tests for shell functions which transform arrays.

Example 337. Test a function which appends a value to an array
testers.testEqualArrayOrMap {
  name = "test-function-add-cowbell";
  valuesArray = [
    "cowbell"
    "cowbell"
  ];
  expectedArray = [
    "cowbell"
    "cowbell"
    "cowbell"
  ];
  script = ''
    addCowbell() {
      local -rn arrayNameRef="$1"
      arrayNameRef+=( "cowbell" )
    }

    nixLog "appending all values in valuesArray to actualArray"
    for value in "''${valuesArray[@]}"; do
      actualArray+=( "$value" )
    done

    nixLog "applying addCowbell"
    addCowbell actualArray
  '';
}

Inputs

NOTE: Internally, this tester uses __structuredAttrs to handle marshalling between Nix expressions and shell variables. This imposes the restriction that arrays and “maps” have values which are string-like.

NOTE: At least one of expectedArray and expectedMap must be provided.

name (string)

The name of the test.

script (string)

The singular task of script is to populate actualArray or actualMap (it may populate both). To do this, script may access the following shell variables:

  • valuesArray (available when valuesArray is provided to the tester)

  • valuesMap (available when valuesMap is provided to the tester)

  • actualArray (available when expectedArray is provided to the tester)

  • actualMap (available when expectedMap is provided to the tester)

While both expectedArray and expectedMap are in scope during the execution of script, they must not be accessed or modified from within script.

valuesArray (array of string-like values, optional)

An array of string-like values. This array may be used within script.

valuesMap (attribute set of string-like values, optional)

An attribute set of string-like values. This attribute set may be used within script.

expectedArray (array of string-like values, optional)

An array of string-like values. This array must not be accessed or modified from within script. When provided, script is expected to populate actualArray.

expectedMap (attribute set of string-like values, optional)

An attribute set of string-like values. This attribute set must not be accessed or modified from within script. When provided, script is expected to populate actualMap.

Return value

The tester produces an empty output and only succeeds when expectedArray and expectedMap match actualArray and actualMap, respectively, when non-null. The build log will contain differences encountered.

testEqualDerivation

Checks that two packages produce the exact same build instructions.

This can be used to make sure that a certain difference of configuration, such as the presence of an overlay does not cause a cache miss.

When the derivations are equal, the return value is an empty file. Otherwise, the build log explains the difference via nix-diff.

Example 338. Check that two packages produce the same derivation
testers.testEqualDerivation "The hello package must stay the same when enabling checks." hello (
  hello.overrideAttrs (o: {
    doCheck = true;
  })
)

invalidateFetcherByDrvHash

Use the derivation hash to invalidate the output via name, for testing.

Type: (a@{ name, ... } -> Derivation) -> a -> Derivation

Normally, fixed output derivations can and should be cached by their output hash only, but for testing we want to re-fetch every time the fetcher changes.

Changes to the fetcher become apparent in the drvPath, which is a hash of how to fetch, rather than a fixed store path. By inserting this hash into the name, we can make sure to re-run the fetcher every time the fetcher changes.

This relies on the assumption that Nix isn’t clever enough to reuse its database of local store contents to optimize fetching.

You might notice that the “salted” name derives from the normal invocation, not the final derivation. invalidateFetcherByDrvHash has to invoke the fetcher function twice: once to get a derivation hash, and again to produce the final fixed output derivation.

Example 339. Prevent nix from reusing the output of a fetcher
{
  tests.fetchgit = testers.invalidateFetcherByDrvHash fetchgit {
    name = "nix-source";
    url = "https://github.com/NixOS/nix";
    rev = "9d9dbe6ed05854e03811c361a3380e09183f4f4a";
    hash = "sha256-7DszvbCNTjpzGRmpIVAWXk20P0/XTrWZ79KSOGLrUWY=";
  };
}

runCommand

runCommand :: { name, script, stdenv ? stdenvNoCC, hash ? "...", ... } -> Derivation

This is a wrapper around pkgs.runCommandWith, which

  • produces a fixed-output derivation, enabling the command(s) to access the network ;

  • salts the derivation’s name based on its inputs, ensuring the command is re-run whenever the inputs change.

It accepts the following attributes:

  • the derivation’s name ;

  • the script to be executed ;

  • stdenv, the environment to use, defaulting to stdenvNoCC ;

  • the derivation’s output hash, defaulting to the empty file’s. The derivation’s outputHashMode is set by default to recursive, so the script can output a directory as well.

All other attributes are passed through to mkDerivation, including nativeBuildInputs to specify dependencies available to the script.

Example 340. Run a command with network access
testers.runCommand {
  name = "access-the-internet";
  script = ''
    curl -o /dev/null https://example.com
    touch $out
  '';
  nativeBuildInputs = with pkgs; [
    cacert
    curl
  ];
}

runNixOSTest

A helper function that behaves exactly like the NixOS runTest, except it also assigns this Nixpkgs package set as the pkgs of the test and makes the nixpkgs.* options read-only.

If your test is part of the Nixpkgs repository, or if you need a more general entrypoint, see “Calling a test” in the NixOS manual.

Example 341. Run a NixOS test using runNixOSTest
pkgs.testers.runNixOSTest (
  { lib, ... }:
  {
    name = "hello";
    nodes.machine =
      { pkgs, ... }:
      {
        environment.systemPackages = [ pkgs.hello ];
      };
    testScript = ''
      machine.succeed("hello")
    '';
  }
)

nixosTest

Run a NixOS VM network test using this evaluation of Nixpkgs.

NOTE: This function is primarily for external use. NixOS itself uses make-test-python.nix directly. Packages defined in Nixpkgs reuse NixOS tests via nixosTests, plural.

It is mostly equivalent to the function import ./make-test-python.nix from the NixOS manual, except that the current application of Nixpkgs (pkgs) will be used, instead of letting NixOS invoke Nixpkgs anew.

If a test machine needs to set NixOS options under nixpkgs, it must set only the nixpkgs.pkgs option.

Parameter

A NixOS VM test network, or path to it. Example:

{
  name = "my-test";
  nodes = {
    machine1 =
      {
        lib,
        pkgs,
        nodes,
        ...
      }:
      {
        environment.systemPackages = [ pkgs.hello ];
        services.foo.enable = true;
      };
    # machine2 = ...;
  };
  testScript = ''
    start_all()
    machine1.wait_for_unit("foo.service")
    machine1.succeed("hello | foo-send")
  '';
}

Result

A derivation that runs the VM test.

Notable attributes:

  • nodes: the evaluated NixOS configurations. Useful for debugging and exploring the configuration.

  • driverInteractive: a script that launches an interactive Python session in the context of the testScript.

Development Shell helpers

The nix-shell command has popularized the concept of transient shell environments for development or testing purposes. However, nix-shell is not the only way to create such environments, and even nix-shell itself can indirectly benefit from this library.

This library provides a set of functions that help create such environments.

devShellTools.valueToString

Converts Nix values to strings in the way the derivation built-in function does.

Example 342. valueToString usage examples
devShellTools.valueToString (builtins.toFile "foo" "bar")
# => "/nix/store/...-foo"
devShellTools.valueToString false
# => ""

devShellTools.unstructuredDerivationInputEnv

Convert a set of derivation attributes (as would be passed to [derivation]) to a set of environment variables that can be used in a shell script. This function does not support __structuredAttrs, but does support passAsFile.

Example 343. unstructuredDerivationInputEnv usage example
devShellTools.unstructuredDerivationInputEnv {
  drvAttrs = {
    name = "foo";
    buildInputs = [
      hello
      figlet
    ];
    builder = bash;
    args = [
      "-c"
      "${./builder.sh}"
    ];
  };
}
# => {
#  name = "foo";
#  buildInputs = "/nix/store/...-hello /nix/store/...-figlet";
#  builder = "/nix/store/...-bash";
#}

Note that args is not included, because Nix does not add it to the builder process environment.


devShellTools.derivationOutputEnv

Takes the relevant parts of a derivation and returns a set of environment variables, that would be present in the derivation.

Example 344. derivationOutputEnv usage example
let
  pkg = hello;
in
devShellTools.derivationOutputEnv {
  outputList = pkg.outputs;
  outputMap = pkg;
}

Special build helpers

This chapter describes several special build helpers.

buildEnv

buildEnv constructs a derivation containing directories and symbolic links, which resembles the profile layout where a list of derivations or store paths are installed.

Unlike symlinkJoin, buildEnv takes special care of the outputs to link and checks for content collisions across the paths by default. A common use case for buildEnv is constructing environment wrappers, such as an interpreter with modules or a program with extensions. For example, python.withPackage is based on buildEnv.

Arguments

buildEnv takes fixed-point arguments (buildEnv (finalAttrs: { })) as well as a plain attribute set.

Unless otherwise noted, arguments can be overridden directly using <pkg>.overrideAttrs.

buildEnv enforces structured attributes ({ __structuredAttrs = true; }).

  • name or pname and version (required): The name of the environment.

  • paths (required): The derivations or store paths to symlink (“install”).

    The elements can be any path-like object that string-interpolates to a store path. The priority of each path is taken from <path>.meta.priority and falls back to lib.meta.defaultPriority if not set.

    The argument paths is passed as attribute passthru.paths to prevent unexpected context pollution. passthru.paths can be overridden with <pkg>.overrideAttrs.

  • extraOutputsToInstall (default to [ ]): Package outputs to include in addition to what meta.outputsToInstall specifies.

  • includeClosures (default to false): Whether to include closures of all input paths. The list of the closure paths are constructed with writeClosure. They are installed with lower priority and with build-time exceptions silenced.

  • extraPrefix (default to ""): Root the result in directory "$out${extraPrefix}", e.g. "/share".

  • ignoreCollisions (default: false): Don’t fail the build upon content collisions.

  • checkCollisionContents (default: true): If there is a collision, check whether the contents and permissions match; and only if not, throw a collision error.

  • ignoreSingleFileOutputs (default: false): Don’t fail the build upon single-file outputs.

  • manifest (default: ""): The manifest file (if any). A symlink $out/manifest will be created to it.

  • pathsToLink (default: [ "/" ]): The paths (relative to each element of paths) that we want to symlink (e.g., ["/bin"]). Any file outside the directories in this list won’t be symlinked into the produced environment.

  • postBuild (default: ""): Shell commands to run after building the symlink tree.

  • passthru and meta (default: { }): stdenv.mkDerivation-supported attributes not passing down to builtins.derivation.

  • derivationArgs (default: { }): Additional stdenv.mkDerivation arguments, such as nativeBuildInputs/buildInputs for postBuild dependencies and setup hooks.

    derivationArgs is not passed down to stdenv.mkDerivation. Override its attributes directly via <pkg>.overrideAttrs and reference directly via finalAttrs.

Build-time exceptions

There are situations where the specified paths might not produce sensible profile layout. By default, the builder fails early upon detecting these exceptions. buildEnv provides arguments to fine-tune or ignore certain exceptions.

Path collisions

Path collisions occur when files provided by two more output paths with the same priority overlap with each other, making the result profile layout potentially affected by the order of elements of paths. This is undesirable in several use cases, such as when paths are determined by merging Nix modules.

If the argument checkCollisionContents is true, the builder checks whether the overlapping paths share the same content and mode, and fails only if not.

The argument ignoreCollisions silence the collision checks and allow the files to be overwritten based on the order of chosen output paths.

In addition to silencing this exception with ignoreCollisions, one can also adjust the priority of colliding packages and store paths. Store paths can specify priority in the form

{
  outPath = <path>;
  meta.priority = <priority>;
}

And lib.meta.setPrio-related Nixpkgs Library functions also apply to a string-like attribute set ({ outPath = <path>; }).

Single-file outputs

When an output path provides a single file instead of a directory, it inherently cannot merge into the result layout. All discoverable packages should configure their meta.outputsToInstall correctly, so that single-file outputs won’t be installed into a profile.

Set ignoreSingleFileOutputs to true to drop all single-file output paths silently. This option is useful when the specified paths contain the output paths of package tests.

fakeNss

Provides /etc/passwd and /etc/group files that contain root and nobody, allowing user/group lookups to work in binaries that insist on doing those. This might be a better choice than a custom script running useradd and related utilities if you only need those files to exist with some entries.

fakeNss also provides /etc/nsswitch.conf, configuring NSS host resolution to first check /etc/hosts before checking DNS, since the default in the absence of a config file (dns [!UNAVAIL=return] files) is quite unexpected.

It also creates an empty directory at /var/empty because it uses that as the home directory for the root and nobody users. The /var/empty directory can also be used as a chroot target to prevent file access in processes that do not need to access files, if your container runs such processes.

The user entries created by fakeNss use the /bin/sh shell, which is not provided by fakeNss because in most cases it won’t be used. If you need that to be available, see dockerTools.binSh or provide your own.

Inputs

fakeNss is made available in Nixpkgs as a package rather than a function, but it has two attributes that can be overridden and might be useful in particular cases. For more details on how overriding works, see Example 346 and the section called “<pkg>.override”.

extraPasswdLines (List of Strings; optional)

A list of lines that will be added to /etc/passwd. Useful if extra users need to exist in the output of fakeNss. If extraPasswdLines is specified, it will not override the root and nobody entries created by fakeNss. Those entries will always exist.

Lines specified here must follow the format in passwd(5).

Default value: [].

extraGroupLines (List of Strings; optional)

A list of lines that will be added to /etc/group. Useful if extra groups need to exist in the output of fakeNss. If extraGroupLines is specified, it will not override the root and nobody entries created by fakeNss. Those entries will always exist.

Lines specified here must follow the format in group(5).

Default value: [].

Examples

Example 345. Using fakeNss with dockerTools.buildImage

This example shows how to use fakeNss as-is. It is useful with functions in dockerTools to allow building Docker images that have the /etc/passwd and /etc/group files. This example includes the hello binary in the image so it can do something besides just have the extra files.

{
  dockerTools,
  fakeNss,
  hello,
}:
dockerTools.buildImage {
  name = "image-with-passwd";
  tag = "latest";

  copyToRoot = [
    fakeNss
    hello
  ];

  config = {
    Cmd = [ "/bin/hello" ];
  };
}

Example 346. Using fakeNss with an override to add extra lines

The following code uses override to add extra lines to /etc/passwd and /etc/group to create another user and group entry.

{ fakeNss }:
fakeNss.override {
  extraPasswdLines = [ "newuser:x:9001:9001:new user:/var/empty:/bin/sh" ];
  extraGroupLines = [ "newuser:x:9001:" ];
}

buildFHSEnv

buildFHSEnv provides a way to build and run an FHS-compatible, lightweight sandbox. It creates an isolated root filesystem with the host’s /nix/store, so its footprint in terms of disk space is quite small. This allows you to run software which is hard or unfeasible to patch for NixOS; 3rd-party source trees with FHS assumptions, games distributed as tarballs, software with integrity checking and/or external self-updated binaries for instance. It uses Linux’ namespaces feature to create temporary lightweight environments which are destroyed after all child processes exit, without requiring elevated privileges. It works similar to containerisation technology such as Docker or FlatPak but provides no security-relevant separation from the host system.

Accepted arguments are:

  • name The name of the environment.

  • pname The pname of the environment.

  • version The version of the environment.

  • executableName The name of the wrapper executable. Defaults to pname if set, or name otherwise.

  • targetPkgs Packages to be installed for the main host’s architecture (i.e. x86_64 on x86_64 installations). Along with libraries, binaries are also installed.

  • multiPkgs Packages to be installed for all architectures supported by a host (i.e. i686 and x86_64 on x86_64 installations). Only libraries are installed by default.

  • multiArch Whether to install 32-bit multiPkgs into the FHSEnv in 64-bit environments

  • extraBuildCommands Additional commands to be executed for finalizing the directory structure.

  • extraBuildCommandsMulti Like extraBuildCommands, but executed only on multilib architectures.

  • extraOutputsToInstall Additional derivation outputs to be linked for both target and multi-architecture packages.

  • extraInstallCommands Additional commands to be executed for finalizing the derivation with runner script.

  • runScript A shell command to be executed inside the sandbox. It defaults to bash. Command line arguments passed to the resulting wrapper are appended to this command by default. This command must be escaped; i.e. "foo app" --do-stuff --with "some file". See lib.escapeShellArgs.

  • profile Optional script for /etc/profile within the sandbox.

You can create a simple environment using a shell.nix like this:

{
  pkgs ? import <nixpkgs> { },
}:

(pkgs.buildFHSEnv {
  name = "simple-x11-env";
  targetPkgs =
    pkgs:
    (with pkgs; [
      udev
      alsa-lib
      libx11
      libxcursor
      libxrandr
    ]);
  multiPkgs =
    pkgs:
    (with pkgs; [
      udev
      alsa-lib
    ]);
  runScript = "bash";
}).env

Running nix-shell on it would drop you into a shell inside an FHS env where those libraries and binaries are available in FHS-compliant paths. Applications that expect an FHS structure (i.e. proprietary binaries) can run inside this environment without modification. You can build a wrapper by running your binary in runScript, e.g. ./bin/start.sh. Relative paths work as expected.

Additionally, the FHS builder links all relocated gsettings-schemas (the glib setup-hook moves them to share/gsettings-schemas/${name}/glib-2.0/schemas) to their standard FHS location. This means you don’t need to wrap binaries with wrapGApps* hook.

pkgs.makeSetupHook

pkgs.makeSetupHook is a build helper that produces hooks that go into nativeBuildInputs

Usage

pkgs.makeSetupHook {
  name = "something-hook";
  propagatedBuildInputs = [ pkgs.commandsomething ];
  depsTargetTargetPropagated = [ pkgs.libsomething ];
} ./script.sh

setup hook that depends on the hello package and runs hello and @shell@ is substituted with path to bash

pkgs.makeSetupHook
  {
    name = "run-hello-hook";
    # Put dependencies here if they have hooks or necessary dependencies propagated
    # otherwise prefer direct paths to executables.
    propagatedBuildInputs = [
      pkgs.hello
      pkgs.cowsay
    ];
    substitutions = {
      shell = "${pkgs.bash}/bin/bash";
      cowsay = "${pkgs.cowsay}/bin/cowsay";
    };
  }
  (
    writeScript "run-hello-hook.sh" ''
      #!@shell@
      # the direct path to the executable has to be here because
      # this will be run when the file is sourced
      # at which point '$PATH' has not yet been populated with inputs
      @cowsay@ cow

      _printHelloHook() {
        hello
      }
      preConfigureHooks+=(_printHelloHook)
    ''
  )

Attributes

  • name Set the name of the hook.

  • propagatedBuildInputs Runtime dependencies (such as binaries) of the hook.

  • depsTargetTargetPropagated Non-binary dependencies.

  • meta

  • passthru

  • substitutions Variables for substituteAll

pkgs.mkShell

pkgs.mkShell is a specialized stdenv.mkDerivation that removes some repetition when using it with nix-shell (or nix develop).

Usage

Here is a common usage example:

{
  pkgs ? import <nixpkgs> { },
}:
pkgs.mkShell {
  packages = [ pkgs.gnumake ];

  inputsFrom = [
    pkgs.hello
    pkgs.gnutar
  ];

  shellHook = ''
    export DEBUG=1
  '';
}

Attributes

  • name (default: nix-shell). Set the name of the derivation.

  • packages (default: []). Add executable packages to the nix-shell environment.

  • inputsFrom (default: []). Add build dependencies of the listed derivations to the nix-shell environment.

  • shellHook (default: ""). Bash statements that are executed by nix-shell.

… all the attributes of stdenv.mkDerivation.

Variants

pkgs.mkShellNoCC is a variant that uses stdenvNoCC instead of stdenv as base environment. This is useful if no C compiler is needed in the shell environment.

Building the shell

This derivation output will contain a text file that contains a reference to all the build inputs. This is useful in CI where we want to make sure that every derivation, and its dependencies, build properly. Or when creating a GC root so that the build dependencies don’t get garbage-collected.

vmTools

A set of VM related utilities, that help in building some packages in more advanced scenarios.

vmTools.createEmptyImage

A bash script fragment that produces a disk image at destination.

Attributes

  • size. The disk size, in MiB.

  • fullName. Name that will be written to ${destination}/nix-support/full-name.

  • destination (optional, default $out). Where to write the image files.

vmTools.runInLinuxVM

Run a derivation in a Linux virtual machine (using Qemu/KVM). By default, there is no disk image; the root filesystem is a tmpfs, and the Nix store is shared with the host (via the 9P protocol). Thus, any pure Nix derivation should run unmodified.

If the build fails and Nix is run with the -K/--keep-failed option, a script run-vm will be left behind in the temporary build directory that allows you to boot into the VM and debug it interactively.

Attributes

  • preVM (optional). Shell command to be evaluated before the VM is started (i.e., on the host).

  • memSize (optional, default 512). The memory size of the VM in MiB (1024×1024 bytes).

  • diskImage (optional). A file system image to be attached to /dev/sda. Note that currently we expect the image to contain a filesystem, not a full disk image with a partition table etc.

Examples

Build the derivation hello inside a VM:

{ pkgs }: with pkgs; with vmTools; runInLinuxVM hello

Build inside a VM with extra memory:

{ pkgs }:
with pkgs;
with vmTools;
runInLinuxVM (
  hello.overrideAttrs (_: {
    memSize = 1024;
  })
)

Use VM with a disk image (implicitly sets diskImage, see vmTools.createEmptyImage):

{ pkgs }:
with pkgs;
with vmTools;
runInLinuxVM (
  hello.overrideAttrs (_: {
    preVM = createEmptyImage {
      size = 1024;
      fullName = "vm-image";
    };
  })
)

vmTools.extractFs

Takes a file, such as an ISO, and extracts its contents into the store.

Attributes

  • file. Path to the file to be extracted. Note that currently we expect the image to contain a filesystem, not a full disk image with a partition table etc.

  • fs (optional). Filesystem of the contents of the file.

Examples

Extract the contents of an ISO file:

{ pkgs }: with pkgs; with vmTools; extractFs { file = ./image.iso; }

vmTools.extractMTDfs

Like the section called “vmTools.extractFs, but it makes use of a Memory Technology Device (MTD).

vmTools.runInLinuxImage

Like the section called “vmTools.runInLinuxVM, but instead of using stdenv from the Nix store, run the build using the tools provided by /bin, /usr/bin, etc. from the specified filesystem image, which typically is a filesystem containing a FHS-based Linux distribution.

vmTools.makeImageTestScript

Generate a script that can be used to run an interactive session in the given image.

Examples

Create a script for running a Fedora 43 VM:

{ pkgs }: pkgs.vmTools.makeImageTestScript pkgs.vmTools.diskImages.fedora43x86_64

Create a script for running an Ubuntu 24.04 VM:

{ pkgs }: pkgs.vmTools.makeImageTestScript pkgs.vmTools.diskImages.ubuntu2404x86_64

vmTools.diskImageFuns

A set of functions that build a predefined set of minimal Linux distributions images.

Images

  • Fedora

    • fedora42x86_64

    • fedora43x86_64

  • Rocky Linux

    • rocky9x86_64

    • rocky10x86_64

  • AlmaLinux

    • alma9x86_64

    • alma10x86_64

  • Oracle Linux

    • oracle9x86_64

  • Amazon Linux

    • amazon2023x86_64

  • Ubuntu

    • ubuntu2204i386

    • ubuntu2204x86_64

    • ubuntu2404x86_64

  • Debian

    • debian11i386

    • debian11x86_64

    • debian12i386

    • debian12x86_64

    • debian13i386

    • debian13x86_64

Attributes

  • size (optional, defaults to 4096). The size of the image, in MiB.

  • extraPackages (optional). A list of names of additional packages from the distribution that should be included in the image.

Examples

8GiB image containing Firefox in addition to the default packages:

{ pkgs }:
pkgs.vmTools.diskImageFuns.ubuntu2404x86_64 {
  extraPackages = [ "firefox" ];
  size = 8192;
}

vmTools.diskImageExtraFuns

Shorthand for vmTools.diskImageFuns.<attr> { extraPackages = ... }.

vmTools.diskImages

Shorthand for vmTools.diskImageFuns.<attr> { }.

pkgs.checkpointBuildTools

pkgs.checkpointBuildTools provides a way to build derivations incrementally. It consists of two functions to make checkpoint builds using Nix possible.

For hermeticity, Nix derivations do not allow any state to be carried over between builds, making a transparent incremental build within a derivation impossible.

However, we can tell Nix explicitly what the previous build state was, by representing that previous state as a derivation output. This allows the passed build state to be used for an incremental build.

To change a normal derivation to a checkpoint-based build, these steps must be taken:

{
  checkpointArtifacts = (pkgs.checkpointBuildTools.prepareCheckpointBuild pkgs.virtualbox);
}
{
  changedVBox = pkgs.virtualbox.overrideAttrs (old: {
    src = path/to/vbox/sources;
  });
}
  • use mkCheckpointBuild changedVBox checkpointArtifacts

  • enjoy shorter build times

Example

{
  pkgs ? import <nixpkgs> { },
}:
let
  inherit (pkgs.checkpointBuildTools) prepareCheckpointBuild mkCheckpointBuild;
  helloCheckpoint = prepareCheckpointBuild pkgs.hello;
  changedHello = pkgs.hello.overrideAttrs (_: {
    doCheck = false;
    postPatch = ''
      sed -i 's/Hello, world!/Hello, Nix!/g' src/hello.c
    '';
  });
in
mkCheckpointBuild changedHello helloCheckpoint

Images

This chapter describes tools for creating various types of images.

pkgs.appimageTools

pkgs.appimageTools is a set of functions for extracting and wrapping AppImage files. They are meant to be used if traditional packaging from source is infeasible, or if it would take too long. To quickly run an AppImage file, pkgs.appimage-run can be used as well.

Warning

The appimageTools API is unstable and may be subject to backwards-incompatible changes in the future.

Wrapping

Use wrapType2 to wrap any AppImage. This will create a FHS environment with many packages expected to exist for the AppImage to work. wrapType2 expects an argument with the src attribute, and either a name attribute or pname and version attributes.

It will eventually call into buildFHSEnv, and any extra attributes in the argument to wrapType2 will be passed through to it. This means that you can pass the extraInstallCommands attribute, for example, and it will have the same effect as described in buildFHSEnv.

Note

In the past, appimageTools provided both wrapType1 and wrapType2, to be used depending on the type of AppImage that was being wrapped. However, those were unified early 2020, meaning that both wrapType1 and wrapType2 have the same behaviour now.

Example 347. Wrapping an AppImage from GitHub
{ appimageTools, fetchurl }:
let
  pname = "nuclear";
  version = "0.6.30";

  src = fetchurl {
    url = "https://github.com/nukeop/nuclear/releases/download/v${version}/nuclear-v${version}.AppImage";
    hash = "sha256-he1uGC1M/nFcKpMM9JKY4oeexJcnzV0ZRxhTjtJz6xw=";
  };
in
appimageTools.wrapType2 { inherit pname version src; }

The argument passed to wrapType2 can also contain an extraPkgs attribute, which allows you to include additional packages inside the FHS environment your AppImage is going to run in. extraPkgs must be a function that returns a list of packages. There are a few ways to learn which dependencies an application needs:

  • Looking through the extracted AppImage files, reading its scripts and running patchelf and ldd on its executables. This can also be done in appimage-run, by setting APPIMAGE_DEBUG_EXEC=bash.

  • Running strace -vfefile on the wrapped executable, looking for libraries that can’t be found.

Example 348. Wrapping an AppImage with extra packages
{ appimageTools, fetchurl }:
let
  pname = "irccloud";
  version = "0.16.0";

  src = fetchurl {
    url = "https://github.com/irccloud/irccloud-desktop/releases/download/v${version}/IRCCloud-${version}-linux-x86_64.AppImage";
    hash = "sha256-/hMPvYdnVB1XjKgU2v47HnVvW4+uC3rhRjbucqin4iI=";
  };
in
appimageTools.wrapType2 {
  inherit pname version src;
  extraPkgs = pkgs: [ pkgs.at-spi2-core ];
}

Extracting

Use extract if you need to extract the contents of an AppImage. This is usually used in Nixpkgs to install extra files in addition to wrapping the AppImage. extract expects an argument with the src attribute, and either a name attribute or pname and version attributes.

Note

In the past, appimageTools provided both extractType1 and extractType2, to be used depending on the type of AppImage that was being extracted. However, those were unified early 2020, meaning that both extractType1 and extractType2 have the same behaviour as extract now.

Example 349. Extracting an AppImage to install extra files

This example was adapted from a real package in Nixpkgs to show how extract is usually used in combination with wrapType2. Note how appimageContents is used in extraInstallCommands to install additional files that were extracted from the AppImage.

{ appimageTools, fetchurl }:
let
  pname = "irccloud";
  version = "0.16.0";

  src = fetchurl {
    url = "https://github.com/irccloud/irccloud-desktop/releases/download/v${version}/IRCCloud-${version}-linux-x86_64.AppImage";
    hash = "sha256-/hMPvYdnVB1XjKgU2v47HnVvW4+uC3rhRjbucqin4iI=";
  };

  appimageContents = appimageTools.extract { inherit pname version src; };
in
appimageTools.wrapType2 {
  inherit pname version src;

  extraPkgs = pkgs: [ pkgs.at-spi2-core ];

  extraInstallCommands = ''
    mv $out/bin/irccloud-${version} $out/bin/irccloud
    install -m 444 -D ${appimageContents}/irccloud.desktop $out/share/applications/irccloud.desktop
    install -m 444 -D ${appimageContents}/usr/share/icons/hicolor/512x512/apps/irccloud.png \
      $out/share/icons/hicolor/512x512/apps/irccloud.png
    substituteInPlace $out/share/applications/irccloud.desktop \
      --replace-fail 'Exec=AppRun' 'Exec=irccloud'
  '';
}

The argument passed to extract can also contain a postExtract attribute, which allows you to execute additional commands after the files are extracted from the AppImage. postExtract must be a string with commands to run.

Warning

When specifying postExtract, you should use appimageTools.wrapAppImage instead of appimageTools.wrapType2. Otherwise wrapType2 will extract the AppImage contents without respecting the postExtract instructions.

Example 350. Extracting an AppImage to install extra files, using postExtract

This is a rewrite of Example 349 to use postExtract and wrapAppImage.

{ appimageTools, fetchurl }:
let
  pname = "irccloud";
  version = "0.16.0";

  src = fetchurl {
    url = "https://github.com/irccloud/irccloud-desktop/releases/download/v${version}/IRCCloud-${version}-linux-x86_64.AppImage";
    hash = "sha256-/hMPvYdnVB1XjKgU2v47HnVvW4+uC3rhRjbucqin4iI=";
  };

  appimageContents = appimageTools.extract {
    inherit pname version src;
    postExtract = ''
      substituteInPlace $out/irccloud.desktop --replace-fail 'Exec=AppRun' 'Exec=irccloud'
    '';
  };
in
appimageTools.wrapAppImage {
  inherit pname version;

  src = appimageContents;

  extraPkgs = pkgs: [ pkgs.at-spi2-core ];

  extraInstallCommands = ''
    mv $out/bin/irccloud-${version} $out/bin/irccloud
    install -m 444 -D ${appimageContents}/irccloud.desktop $out/share/applications/irccloud.desktop
    install -m 444 -D ${appimageContents}/usr/share/icons/hicolor/512x512/apps/irccloud.png \
      $out/share/icons/hicolor/512x512/apps/irccloud.png
  '';

  # specify src archive for nix-update
  passthru.src = src;
}

pkgs.dockerTools

pkgs.dockerTools is a set of functions for creating and manipulating Docker images according to the Docker Image Specification v1.3.1. Docker itself is not used to perform any of the operations done by these functions.

buildImage

This function builds a Docker-compatible repository tarball containing a single image. As such, the result is suitable for being loaded in Docker with docker image load (see Example 351 for how to do this).

This function will create a single layer for all files (and dependencies) that are specified in its argument. Only new dependencies that are not already in the existing layers will be copied. If you prefer to create multiple layers for the files and dependencies you want to add to the image, see the section called “buildLayeredImage” or the section called “streamLayeredImage” instead.

This function allows a script to be run during the layer generation process, allowing custom behaviour to affect the final results of the image (see the documentation of the runAsRoot and extraCommands attributes).

The resulting repository tarball will list a single image as specified by the name and tag attributes. By default, that image will use a static creation date (see documentation for the created attribute). This allows buildImage to produce reproducible images.

Tip

When running an image built with buildImage, you might encounter certain errors depending on what you included in the image, especially if you did not start with any base image.

If you encounter errors similar to getProtocolByName: does not exist (no such protocol name: tcp), you may need to add the contents of pkgs.iana-etc in the copyToRoot attribute. Similarly, if you encounter errors similar to Error_Protocol ("certificate has unknown CA",True,UnknownCa), you may need to add the contents of pkgs.cacert in the copyToRoot attribute.

Inputs

buildImage expects an argument with the following attributes:

name (String)

The name of the generated image.

tag (String or Null; optional)

Tag of the generated image. If null, the hash of the nix derivation will be used as the tag.

Default value: null.

fromImage (Path or Null; optional)

The repository tarball of an image to be used as the base for the generated image. It must be a valid Docker image, such as one exported by docker image save, or another image built with the dockerTools utility functions. This can be seen as an equivalent of FROM fromImage in a Dockerfile. A value of null can be seen as an equivalent of FROM scratch.

If specified, the layer created by buildImage will be appended to the layers defined in the base image, resulting in an image with at least two layers (one or more layers from the base image and the layer created by buildImage). Otherwise, the resulting image will contain the single layer created by buildImage.

Note

Only Env configuration is inherited from the base image.

Default value: null.

fromImageName (String or Null; optional)

Used to specify the image within the repository tarball in case it contains multiple images. A value of null means that buildImage will use the first image available in the repository.

Note

This must be used with fromImageTag. Using only fromImageName without fromImageTag will make buildImage use the first image available in the repository.

Default value: null.

fromImageTag (String or Null; optional)

Used to specify the image within the repository tarball in case it contains multiple images. A value of null means that buildImage will use the first image available in the repository.

Note

This must be used with fromImageName. Using only fromImageTag without fromImageName will make buildImage use the first image available in the repository.

Default value: null.

copyToRoot (Path, List of Paths, or Null; optional)

Files to add to the generated image. Anything that coerces to a path (e.g. a derivation) can also be used. This can be seen as an equivalent of ADD contents/ / in a Dockerfile.

Default value: null.

keepContentsDirlinks (Boolean; optional)

When adding files to the generated image (as specified by copyToRoot), this attribute controls whether to preserve symlinks to directories. If false, the symlinks will be transformed into directories. This behaves the same as rsync -k when keepContentsDirlinks is false, and the same as rsync -K when keepContentsDirlinks is true.

Default value: false.

runAsRoot (String or Null; optional)

A bash script that will run as root inside a VM that contains the existing layers of the base image and the new generated layer (including the files from copyToRoot). The script will be run with a working directory of /. This can be seen as an equivalent of RUN ... in a Dockerfile. A value of null means that this step in the image generation process will be skipped.

See Example 352 for how to work with this attribute.

Caution

Using this attribute requires the kvm device to be available, see system-features. If the kvm device isn’t available, you should consider using buildLayeredImage or streamLayeredImage instead. Those functions allow scripts to be run as root without access to the kvm device.

Note

At the time the script in runAsRoot is run, the files specified directly in copyToRoot will be present in the VM, but their dependencies might not be there yet. Copying their dependencies into the generated image is a step that happens after runAsRoot finishes running.

Default value: null.

extraCommands (String; optional)

A bash script that will run before the layer created by buildImage is finalised. The script will be run on some (opaque) working directory which will become / once the layer is created. This is similar to runAsRoot, but the script specified in extraCommands is not run as root, and does not involve creating a VM. It is simply run as part of building the derivation that outputs the layer created by buildImage.

See Example 353 for how to work with this attribute, and subtle differences compared to runAsRoot.

Default value: "".

config (Attribute Set or Null; optional)

Used to specify the configuration of the containers that will be started off the generated image. Must be an attribute set, with each attribute as listed in the Docker Image Specification v1.3.1.

Default value: null.

architecture (String; optional)

Used to specify the image architecture. This is useful for multi-architecture builds that don’t need cross compiling. If specified, its value should follow the OCI Image Configuration Specification, which should still be compatible with Docker. According to the linked specification, all possible values for $GOARCH in the Go docs should be valid, but will commonly be one of 386, amd64, arm, or arm64.

Default value: the same value from pkgs.go.GOARCH.

diskSize (Number; optional)

Controls the disk size in MiB (1024x1024 bytes) of the VM used to run the script specified in runAsRoot. This attribute is ignored if runAsRoot is null.

Default value: 1024.

buildVMMemorySize (Number; optional)

Controls the amount of memory in MiB (1024x1024 bytes) provisioned for the VM used to run the script specified in runAsRoot. This attribute is ignored if runAsRoot is null.

Default value: 512.

created (String; optional)

Specifies the time of creation of the generated image. This should be either a date and time formatted according to ISO-8601 or "now", in which case buildImage will use the current date.

See Example 354 for how to use "now".

Caution

Using "now" means that the generated image will not be reproducible anymore (because the date will always change whenever it’s built).

Default value: "1970-01-01T00:00:01Z".

uid (Number; optional)

The uid of the user that will own the files packed in the new layer built by buildImage.

Default value: 0.

gid (Number; optional)

The gid of the group that will own the files packed in the new layer built by buildImage.

Default value: 0.

compressor (String; optional)

Selects the algorithm used to compress the image.

Default value: "gz".
Possible values: "none", "gz", "zstd".

includeNixDB (Boolean; optional)

Populate the nix database in the image with the dependencies of copyToRoot. The main purpose is to be able to use nix commands in the container.

Caution

Be careful since this doesn’t work well in combination with fromImage. In particular, in a multi-layered image, only the Nix paths from the lower image will be in the database.

This also neglects to register the store paths that are pulled into the image as a dependency of one of the other values, but aren’t a dependency of copyToRoot.

Default value: false.

meta (Attribute Set)

The meta attribute of the resulting derivation, as in stdenv.mkDerivation. Accepts description, maintainers and any other meta attributes.

contents DEPRECATED

This attribute is deprecated, and users are encouraged to use copyToRoot instead.

Passthru outputs

buildImage defines a few passthru attributes:

buildArgs (Attribute Set)

The argument passed to buildImage itself. This allows you to inspect all attributes specified in the argument, as described above.

layer (Attribute Set)

The derivation with the layer created by buildImage. This allows easier inspection of the contents added by buildImage in the generated image.

imageTag (String)

The tag of the generated image. This is useful if no tag was specified in the attributes of the argument to buildImage, because an automatic tag will be used instead. imageTag allows you to retrieve the value of the tag used in this case.

Examples

Example 351. Building a Docker image

The following package builds a Docker image that runs the redis-server executable from the redis package. The Docker image will have name redis and tag latest.

{
  dockerTools,
  buildEnv,
  redis,
}:
dockerTools.buildImage {
  name = "redis";
  tag = "latest";

  copyToRoot = buildEnv {
    name = "image-root";
    paths = [ redis ];
    pathsToLink = [ "/bin" ];
  };

  runAsRoot = ''
    mkdir -p /data
  '';

  config = {
    Cmd = [ "/bin/redis-server" ];
    WorkingDir = "/data";
    Volumes = {
      "/data" = { };
    };
  };
}

The result of building this package is a .tar.gz file that can be loaded into Docker:

$ nix-build
(some output removed for clarity)
building '/nix/store/yw0adm4wpsw1w6j4fb5hy25b3arr9s1v-docker-image-redis.tar.gz.drv'...
Adding layer...
tar: Removing leading `/' from member names
Adding meta...
Cooking the image...
Finished.
/nix/store/p4dsg62inh9d2ksy3c7bv58xa851dasr-docker-image-redis.tar.gz

$ docker image load -i /nix/store/p4dsg62inh9d2ksy3c7bv58xa851dasr-docker-image-redis.tar.gz
(some output removed for clarity)
Loaded image: redis:latest

Example 352. Building a Docker image with runAsRoot

The following package builds a Docker image with the hello executable from the hello package. It uses runAsRoot to create a directory and a file inside the image.

This works the same as Example 353, but uses runAsRoot instead of extraCommands.

{
  dockerTools,
  buildEnv,
  hello,
}:
dockerTools.buildImage {
  name = "hello";
  tag = "latest";

  copyToRoot = buildEnv {
    name = "image-root";
    paths = [ hello ];
    pathsToLink = [ "/bin" ];
  };

  runAsRoot = ''
    mkdir -p /data
    echo "some content" > my-file
  '';

  config = {
    Cmd = [ "/bin/hello" ];
    WorkingDir = "/data";
  };
}

Example 353. Building a Docker image with extraCommands

The following package builds a Docker image with the hello executable from the hello package. It uses extraCommands to create a directory and a file inside the image.

This works the same as Example 352, but uses extraCommands instead of runAsRoot. Note that with extraCommands, we can’t directly reference / and must create files and directories as if we were already on /.

{
  dockerTools,
  buildEnv,
  hello,
}:
dockerTools.buildImage {
  name = "hello";
  tag = "latest";

  copyToRoot = buildEnv {
    name = "image-root";
    paths = [ hello ];
    pathsToLink = [ "/bin" ];
  };

  extraCommands = ''
    mkdir -p data
    echo "some content" > my-file
  '';

  config = {
    Cmd = [ "/bin/hello" ];
    WorkingDir = "/data";
  };
}

Example 354. Building a Docker image with a creation date set to the current time

Note that using a value of "now" in the created attribute will break reproducibility.

{
  dockerTools,
  buildEnv,
  hello,
}:
dockerTools.buildImage {
  name = "hello";
  tag = "latest";

  created = "now";

  copyToRoot = buildEnv {
    name = "image-root";
    paths = [ hello ];
    pathsToLink = [ "/bin" ];
  };

  config.Cmd = [ "/bin/hello" ];
}

After importing the generated repository tarball with Docker, its CLI will display a reasonable date and sort the images as expected:

$ docker image ls
REPOSITORY   TAG      IMAGE ID       CREATED              SIZE
hello        latest   de2bf4786de6   About a minute ago   25.2MB

buildLayeredImage

buildLayeredImage uses streamLayeredImage underneath to build a compressed Docker-compatible repository tarball. Basically, buildLayeredImage runs the script created by streamLayeredImage to save the compressed image in the Nix store. buildLayeredImage supports the same options as streamLayeredImage, see streamLayeredImage for details.

Note

Despite the similar name, buildImage works completely differently from buildLayeredImage and streamLayeredImage.

Even though some of the arguments may seem related, they cannot be interchanged.

You can load the result of this function in Docker with docker image load. See Example 355 to see how to do that.

Examples

Example 355. Building a layered Docker image

The following package builds a layered Docker image that runs the hello executable from the hello package. The Docker image will have name hello and tag latest.

{ dockerTools, hello }:
dockerTools.buildLayeredImage {
  name = "hello";
  tag = "latest";

  contents = [ hello ];

  config.Cmd = [ "/bin/hello" ];
}

The result of building this package is a .tar.gz file that can be loaded into Docker:

$ nix-build
(some output removed for clarity)
building '/nix/store/bk8bnrbw10nq7p8pvcmdr0qf57y6scha-hello.tar.gz.drv'...
No 'fromImage' provided
Creating layer 1 from paths: ['/nix/store/i93s7xxblavsacpy82zdbn4kplsyq48l-libunistring-1.1']
Creating layer 2 from paths: ['/nix/store/ji01n9vinnj22nbrb86nx8a1ssgpilx8-libidn2-2.3.4']
Creating layer 3 from paths: ['/nix/store/ldrslljw4rg026nw06gyrdwl78k77vyq-xgcc-12.3.0-libgcc']
Creating layer 4 from paths: ['/nix/store/9y8pmvk8gdwwznmkzxa6pwyah52xy3nk-glibc-2.38-27']
Creating layer 5 from paths: ['/nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1']
Creating layer 6 with customisation...
Adding manifests...
Done.
/nix/store/hxcz7snvw7f8rzhbh6mv8jq39d992905-hello.tar.gz

$ docker image load -i /nix/store/hxcz7snvw7f8rzhbh6mv8jq39d992905-hello.tar.gz
(some output removed for clarity)
Loaded image: hello:latest

streamLayeredImage

streamLayeredImage builds a script which, when run, will stream to stdout a Docker-compatible repository tarball containing a single image, using multiple layers to improve sharing between images. This means that streamLayeredImage does not output an image into the Nix store, but only a script that builds the image, saving on IO and disk/cache space, particularly with large images.

You can load the result of this function in Docker with docker image load. See Example 356 to see how to do that.

For this function, you specify a store path or a list of store paths to be added to the image, and the functions will automatically include any dependencies of those paths in the image. The function will attempt to create one layer per object in the Nix store that needs to be added to the image. In case there are more objects to include than available layers, the function will put the most “popular” objects in their own layers, and group all remaining objects into a single layer.

An additional layer will be created with symlinks to the store paths you specified to be included in the image. These symlinks are built with symlinkJoin, so they will be included in the root of the image. See Example 357 to understand how these symlinks are laid out in the generated image.

streamLayeredImage allows scripts to be run when creating the additional layer with symlinks, allowing custom behaviour to affect the final results of the image (see the documentation of the extraCommands and fakeRootCommands attributes).

The resulting repository tarball will list a single image as specified by the name and tag attributes. By default, that image will use a static creation date (see documentation for the created and mtime attributes). This allows the function to produce reproducible images.

Inputs

streamLayeredImage expects one argument with the following attributes:

name (String)

The name of the generated image.

tag (String or Null; optional)

Tag of the generated image. If null, the hash of the nix derivation will be used as the tag.

Default value: null.

fromImage(Path or Null; optional)

The repository tarball of an image to be used as the base for the generated image. It must be a valid Docker image, such as one exported by docker image save, or another image built with the dockerTools utility functions. This can be seen as an equivalent of FROM fromImage in a Dockerfile. A value of null can be seen as an equivalent of FROM scratch.

If specified, the created layers will be appended to the layers defined in the base image.

Default value: null.

contents (Path or List of Paths; optional)

Directories whose contents will be added to the generated image. Things that coerce to paths (e.g. a derivation) can also be used. This can be seen as an equivalent of ADD contents/ / in a Dockerfile.

All the contents specified by contents will be added as a final layer in the generated image. They will be added as links to the actual files (e.g., links to the store paths). The actual files will be added in previous layers.

Default value: []

config (Attribute Set or Null; optional)

Used to specify the configuration of the containers that will be started off the generated image. Must be an attribute set, with each attribute as listed in the Docker Image Specification v1.3.0.

If any packages are used directly in config, they will be automatically included in the generated image. See Example 358 for an example.

Default value: null.

architecture (String; optional)

Used to specify the image architecture. This is useful for multi-architecture builds that don’t need cross compiling. If specified, its value should follow the OCI Image Configuration Specification, which should still be compatible with Docker. According to the linked specification, all possible values for $GOARCH in the Go docs should be valid, but will commonly be one of 386, amd64, arm, or arm64.

Default value: the same value from pkgs.go.GOARCH.

created (String; optional)

Specifies the time of creation of the generated image. This date will be used for the image metadata. This should be either a date and time formatted according to ISO-8601 or "now", in which case the current date will be used.

Caution

Using "now" means that the generated image will not be reproducible anymore (because the date will always change whenever it’s built).

Default value: "1970-01-01T00:00:01Z".

mtime (String; optional)

Specifies the time used for the modification timestamp of files within the layers of the generated image. This should be either a date and time formatted according to ISO-8601 or "now", in which case the current date will be used.

Caution

Using a non-constant date will cause built layers to have a different hash each time, preventing deduplication. Using "now" also means that the generated image will not be reproducible anymore (because the date will always change whenever it’s built).

Default value: "1970-01-01T00:00:01Z".

uid (Number; optional) gid (Number; optional) uname (String; optional) gname (String; optional)

: Credentials for Nix store ownership. Can be overridden to, e.g., 1000 / 1000 / "user" / "user" to enable building a container where Nix can be used as an unprivileged user in single-user mode.

Default value: 0 / 0 / "root" / "root"

maxLayers (Number; optional)

The maximum number of layers that will be used by the generated image. If a fromImage was specified, the number of layers used by fromImage will be subtracted from maxLayers to ensure that the image generated will have at most maxLayers.

Caution

Depending on the tool/runtime where the image will be used, there might be a limit to the number of layers that an image can have. For Docker, see this issue on GitHub.

Default value: 100.

extraCommands (String; optional)

A bash script that will run in the context of the layer created with the contents specified by contents. At the moment this script runs, only the contents directly specified by contents will be available as links.

Default value: "".

fakeRootCommands (String; optional)

A bash script that will run in the context of the layer created with the contents specified by contents. During the process to generate that layer, the script in extraCommands will be run first, if specified. After that, a fakeroot(1) environment will be entered. The script specified in fakeRootCommands runs inside the fakeroot environment, and the layer is then generated from the view of the files inside the fakeroot environment.

This is useful to change the owners of the files in the layer (by running chown, for example), or performing any other privileged operations related to file manipulation (by default, all files in the layer will be owned by root, and the build environment doesn’t have enough privileges to directly perform privileged operations on these files).

For more details, see the manpage for fakeroot(1).

Caution

Due to how fakeroot works, static binaries cannot perform privileged file operations in fakeRootCommands, unless enableFakechroot is set to true.

Default value: "".

enableFakechroot (Boolean; optional)

By default, the script specified in fakeRootCommands only runs inside a fakeroot environment. If enableFakechroot is true, a more complete chroot environment will be created using proot before running the script in fakeRootCommands. Files in the Nix store will be available. This allows scripts that perform installation in / to work as expected. This can be seen as an equivalent of RUN ... in a Dockerfile.

Default value: false

includeStorePaths (Boolean; optional)

The files specified in contents are put into layers in the generated image. If includeStorePaths is false, the actual files will not be included in the generated image, and only links to them will be added instead. It is not recommended to set this to false unless you have other tooling to insert the store paths via other means (such as bind mounting the host store) when running containers with the generated image. If you don’t provide any extra tooling, the generated image won’t run properly.

See Example 357 to understand the impact of setting includeStorePaths to false.

Default value: true

includeNixDB (Boolean; optional)

Populate the nix database in the image with the dependencies of copyToRoot. The main purpose is to be able to use nix commands in the container.

Caution

Be careful since this doesn’t work well in combination with fromImage. In particular, in a multi-layered image, only the Nix paths from the lower image will be in the database.

This also neglects to register the store paths that are pulled into the image as a dependency of one of the other values, but aren’t a dependency of copyToRoot.

Default value: false.

meta (Attribute Set)

The meta attribute of the resulting derivation, as in stdenv.mkDerivation. Accepts description, maintainers and any other meta attributes.

passthru (Attribute Set; optional)

Use this to pass any attributes as passthru for the resulting derivation.

Default value: {}

Passthru outputs

streamLayeredImage also defines its own passthru attributes:

imageTag (String)

The tag of the generated image. This is useful if no tag was specified in the attributes of the argument to the function, because an automatic tag will be used instead. imageTag allows you to retrieve the value of the tag used in this case.

Examples

Example 356. Streaming a layered Docker image

The following package builds a script which, when run, will stream a layered Docker image that runs the hello executable from the hello package. The Docker image will have name hello and tag latest.

{ dockerTools, hello }:
dockerTools.streamLayeredImage {
  name = "hello";
  tag = "latest";

  contents = [ hello ];

  config.Cmd = [ "/bin/hello" ];
}

The result of building this package is a script. Running this script and piping it into docker image load gives you the same image that was built in Example 355. Note that in this case, the image is never added to the Nix store, but instead streamed directly into Docker.

$ nix-build
(output removed for clarity)
/nix/store/wsz2xl8ckxnlb769irvq6jv1280dfvxd-stream-hello

$ /nix/store/wsz2xl8ckxnlb769irvq6jv1280dfvxd-stream-hello | docker image load
No 'fromImage' provided
Creating layer 1 from paths: ['/nix/store/i93s7xxblavsacpy82zdbn4kplsyq48l-libunistring-1.1']
Creating layer 2 from paths: ['/nix/store/ji01n9vinnj22nbrb86nx8a1ssgpilx8-libidn2-2.3.4']
Creating layer 3 from paths: ['/nix/store/ldrslljw4rg026nw06gyrdwl78k77vyq-xgcc-12.3.0-libgcc']
Creating layer 4 from paths: ['/nix/store/9y8pmvk8gdwwznmkzxa6pwyah52xy3nk-glibc-2.38-27']
Creating layer 5 from paths: ['/nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1']
Creating layer 6 with customisation...
Adding manifests...
Done.
(some output removed for clarity)
Loaded image: hello:latest

Example 357. Exploring the layers in an image built with streamLayeredImage

Assume the following package, which builds a layered Docker image with the hello package.

{ dockerTools, hello }:
dockerTools.streamLayeredImage {
  name = "hello";
  contents = [ hello ];
}

The hello package depends on 4 other packages:

$ nix-store --query -R $(nix-build -A hello)
/nix/store/i93s7xxblavsacpy82zdbn4kplsyq48l-libunistring-1.1
/nix/store/ji01n9vinnj22nbrb86nx8a1ssgpilx8-libidn2-2.3.4
/nix/store/ldrslljw4rg026nw06gyrdwl78k77vyq-xgcc-12.3.0-libgcc
/nix/store/9y8pmvk8gdwwznmkzxa6pwyah52xy3nk-glibc-2.38-27
/nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1

This means that all these packages will be included in the image generated by streamLayeredImage. It will put each package in its own layer, for a total of 5 layers with actual files in them. A final layer will be created only with symlinks for the hello package.

The image generated will have the following directory structure (some directories were collapsed for readability):

├── bin
│   └── hello → /nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1/bin/hello
├── nix
│   └── store
│       ├─⊕ 9y8pmvk8gdwwznmkzxa6pwyah52xy3nk-glibc-2.38-27
│       ├─⊕ i93s7xxblavsacpy82zdbn4kplsyq48l-libunistring-1.1
│       ├─⊕ ji01n9vinnj22nbrb86nx8a1ssgpilx8-libidn2-2.3.4
│       ├─⊕ ldrslljw4rg026nw06gyrdwl78k77vyq-xgcc-12.3.0-libgcc
│       └─⊕ zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1
└── share
    ├── info
    │   └── hello.info → /nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1/share/info/hello.info
    ├─⊕ locale
    └── man
        └── man1
            └── hello.1.gz → /nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1/share/man/man1/hello.1.gz

Each of the packages in /nix/store comes from a layer in the image. The final layer adds the /bin and /share directories, but they only contain links to the actual files in /nix/store.

If our package sets includeStorePaths to false, we’ll end up with only the final layer with the links, but the actual files won’t exist in the image:

{ dockerTools, hello }:
dockerTools.streamLayeredImage {
  name = "hello";
  contents = [ hello ];
  includeStorePaths = false;
}

After building this package, the image will have the following directory structure:

├── bin
│   └── hello → /nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1/bin/hello
└── share
    ├── info
    │   └── hello.info → /nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1/share/info/hello.info
    ├─⊕ locale
    └── man
        └── man1
            └── hello.1.gz → /nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1/share/man/man1/hello.1.gz

Note how the links point to paths in /nix/store, but they’re not included in the image itself. This is why you need extra tooling when using includeStorePaths: a container created from such image won’t find any of the files it needs to run otherwise.


Example 358. Building a layered Docker image with packages directly in config

The closure of config is automatically included in the generated image. The following package shows a more compact way to create the same output generated in Example 356.

{
  dockerTools,
  hello,
  lib,
}:
dockerTools.streamLayeredImage {
  name = "hello";
  tag = "latest";
  config.Cmd = [ "${lib.getExe hello}" ];
}

pullImage

This function is similar to the docker image pull command, which means it can be used to pull a Docker image from a registry that implements the Docker Registry HTTP API V2. By default, the docker.io registry is used.

The image will be downloaded as an uncompressed Docker-compatible repository tarball, which is suitable for use with other dockerTools functions such as buildImage, buildLayeredImage, and streamLayeredImage.

This function requires two different types of hashes/digests to be specified:

  • One of them is used to identify a unique image within the registry (see the documentation for the imageDigest attribute).

  • The other is used by Nix to ensure the contents of the output haven’t changed (see the documentation for the sha256 attribute).

Both hashes are required because they must uniquely identify some content in two completely different systems (the Docker registry and the Nix store), but their values will not be the same. See Example 361 for a tool that can help gather these values.

Inputs

pullImage expects a single argument with the following attributes:

imageName (String)

Specifies the name of the image to be downloaded, as well as the registry endpoint. By default, the docker.io registry is used. To specify a different registry, prepend the endpoint to imageName, separated by a slash (/). See Example 360 for how to do that.

imageDigest (String)

Specifies the digest of the image to be downloaded.

Tip

Why can’t I specify a tag to pull from, and have to use a digest instead?

Tags are often updated to point to different image contents. The most common example is the latest tag, which is usually updated whenever a newer image version is available.

An image tag isn’t enough to guarantee the contents of an image won’t change, but a digest guarantees this. Providing a digest helps ensure that you will still be able to build the same Nix code and get the same output even if newer versions of an image are released.

sha256 (String)

The hash of the image after it is downloaded. Internally, this is passed to the outputHash attribute of the resulting derivation. This is needed to provide a guarantee to Nix that the contents of the image haven’t changed, because Nix doesn’t support the value in imageDigest.

finalImageName (String; optional)

Specifies the name that will be used for the image after it has been downloaded. This only applies after the image is downloaded, and is not used to identify the image to be downloaded in the registry. Use imageName for that instead.

Default value: the same value specified in imageName.

finalImageTag (String; optional)

Specifies the tag that will be used for the image after it has been downloaded. This only applies after the image is downloaded, and is not used to identify the image to be downloaded in the registry.

Default value: "latest".

os (String; optional)

Specifies the operating system of the image to pull. If specified, its value should follow the OCI Image Configuration Specification, which should still be compatible with Docker. According to the linked specification, all possible values for $GOOS in the Go docs should be valid, but will commonly be one of darwin or linux.

Default value: "linux".

arch (String; optional)

Specifies the architecture of the image to pull. If specified, its value should follow the OCI Image Configuration Specification, which should still be compatible with Docker. According to the linked specification, all possible values for $GOARCH in the Go docs should be valid, but will commonly be one of 386, amd64, arm, or arm64.

Default value: the same value from pkgs.go.GOARCH.

tlsVerify (Boolean; optional)

Used to enable or disable HTTPS and TLS certificate verification when communicating with the chosen Docker registry. Setting this to false will make pullImage connect to the registry through HTTP.

Default value: true.

name (String; optional)

The name used for the output in the Nix store path.

Default value: a value derived from finalImageName and finalImageTag, with some symbols replaced. It is recommended to treat the default as an opaque value.

Examples

Example 359. Pulling the nixos/nix Docker image from the default registry

This example pulls the nixos/nix image and saves it in the Nix store.

{ dockerTools }:
dockerTools.pullImage {
  imageName = "nixos/nix";
  imageDigest = "sha256:b8ea88f763f33dfda2317b55eeda3b1a4006692ee29e60ee54ccf6d07348c598";
  finalImageName = "nix";
  finalImageTag = "2.19.3";
  hash = "sha256-zRwlQs1FiKrvHPaf8vWOR/Tlp1C5eLn1d9pE4BZg3oA=";
}

Example 360. Pulling the nixos/nix Docker image from a specific registry

This example pulls the coreos/etcd image from the quay.io registry.

{ dockerTools }:
dockerTools.pullImage {
  imageName = "quay.io/coreos/etcd";
  imageDigest = "sha256:24a23053f29266fb2731ebea27f915bb0fb2ae1ea87d42d890fe4e44f2e27c5d";
  finalImageName = "etcd";
  finalImageTag = "v3.5.11";
  hash = "sha256-Myw+85f2/EVRyMB3axECdmQ5eh9p1q77FWYKy8YpRWU=";
}

Example 361. Finding the digest and hash values to use for dockerTools.pullImage

Since dockerTools.pullImage requires two different hashes, one can run the nix-prefetch-docker tool to find out the values for the hashes. The tool outputs some text for an attribute set which you can pass directly to pullImage.

$ nix run nixpkgs#nix-prefetch-docker -- --image-name nixos/nix --image-tag 2.19.3 --arch amd64 --os linux
(some output removed for clarity)
Writing manifest to image destination
-> ImageName: nixos/nix
-> ImageDigest: sha256:498fa2d7f2b5cb3891a4edf20f3a8f8496e70865099ba72540494cd3e2942634
-> FinalImageName: nixos/nix
-> FinalImageTag: latest
-> ImagePath: /nix/store/4mxy9mn6978zkvlc670g5703nijsqc95-docker-image-nixos-nix-latest.tar
-> ImageHash: 1q6cf2pdrasa34zz0jw7pbs6lvv52rq2aibgxccbwcagwkg2qj1q
{
  imageName = "nixos/nix";
  imageDigest = "sha256:498fa2d7f2b5cb3891a4edf20f3a8f8496e70865099ba72540494cd3e2942634";
  hash = "sha256-OEgs3uRPMb4Y629FJXAWZW9q9LqHS/A/GUqr3K5wzOA=";
  finalImageName = "nixos/nix";
  finalImageTag = "latest";
}

It is important to supply the --arch and --os arguments to nix-prefetch-docker to filter to a single image, in case there are multiple architectures and/or operating systems supported by the image name and tags specified. By default, nix-prefetch-docker will set os to linux and arch to amd64.

Run nix-prefetch-docker --help for a list of all supported arguments:

$ nix run nixpkgs#nix-prefetch-docker -- --help
(output removed for clarity)

exportImage

This function is similar to the docker container export command, which means it can be used to export an image’s filesystem as an uncompressed tarball archive. The difference is that docker container export is applied to containers, but dockerTools.exportImage applies to Docker images. The resulting archive will not contain any image metadata (such as command to run with docker container run), only the filesystem contents.

You can use this function to import an archive in Docker with docker image import. See Example 363 to understand how to do that.

Caution

exportImage works by unpacking the given image inside a VM. Because of this, using this function requires the kvm device to be available, see system-features.

Inputs

exportImage expects an argument with the following attributes:

fromImage (Attribute Set or String)

The repository tarball of the image whose filesystem will be exported. It must be a valid Docker image, such as one exported by docker image save, or another image built with the dockerTools utility functions.

If name is not specified, fromImage must be an Attribute Set corresponding to a derivation, i.e. it can’t be a path to a tarball. If name is specified, fromImage can be either an Attribute Set corresponding to a derivation or simply a path to a tarball.

See Example 364 and Example 365 to understand the connection between fromImage, name, and the name used for the output of exportImage.

fromImageName (String or Null; optional)

Used to specify the image within the repository tarball in case it contains multiple images. A value of null means that exportImage will use the first image available in the repository.

Note

This must be used with fromImageTag. Using only fromImageName without fromImageTag will make exportImage use the first image available in the repository.

Default value: null.

fromImageTag (String or Null; optional)

Used to specify the image within the repository tarball in case it contains multiple images. A value of null means that exportImage will use the first image available in the repository.

Note

This must be used with fromImageName. Using only fromImageTag without fromImageName will make exportImage use the first image available in the repository.

Default value: null.

diskSize (Number; optional)

Controls the disk size (in megabytes) of the VM used to unpack the image.

Default value: 1024.

name (String; optional)

The name used for the output in the Nix store path.

Default value: the value of fromImage.name.

Examples

Example 362. Exporting a Docker image with dockerTools.exportImage

This example first builds a layered image with dockerTools.buildLayeredImage, and then exports its filesystem with dockerTools.exportImage.

{ dockerTools, hello }:
dockerTools.exportImage {
  name = "hello";
  fromImage = dockerTools.buildLayeredImage {
    name = "hello";
    contents = [ hello ];
  };
}

When building the package above, we can see the layers of the Docker image being unpacked to produce the final output:

$ nix-build
(some output removed for clarity)
Unpacking base image...
From-image name or tag wasn't set. Reading the first ID.
Unpacking layer 5731199219418f175d1580dbca05677e69144425b2d9ecb60f416cd57ca3ca42/layer.tar
tar: Removing leading `/' from member names
Unpacking layer e2897bf34bb78c4a65736510204282d9f7ca258ba048c183d665bd0f3d24c5ec/layer.tar
tar: Removing leading `/' from member names
Unpacking layer 420aa5876dca4128cd5256da7dea0948e30ef5971712f82601718cdb0a6b4cda/layer.tar
tar: Removing leading `/' from member names
Unpacking layer ea5f4e620e7906c8ecbc506b5e6f46420e68d4b842c3303260d5eb621b5942e5/layer.tar
tar: Removing leading `/' from member names
Unpacking layer 65807b9abe8ab753fa97da8fb74a21fcd4725cc51e1b679c7973c97acd47ebcf/layer.tar
tar: Removing leading `/' from member names
Unpacking layer b7da2076b60ebc0ea6824ef641978332b8ac908d47b2d07ff31b9cc362245605/layer.tar
Executing post-mount steps...
Packing raw image...
[    1.660036] reboot: Power down
/nix/store/x6a5m7c6zdpqz1d8j7cnzpx9glzzvd2h-hello

The following command lists some of the contents of the output to verify that the structure of the archive is as expected:

$ tar --exclude '*/share/*' --exclude 'nix/store/*/*' -tvf /nix/store/x6a5m7c6zdpqz1d8j7cnzpx9glzzvd2h-hello
drwxr-xr-x root/0            0 1979-12-31 16:00 ./
drwxr-xr-x root/0            0 1979-12-31 16:00 ./bin/
lrwxrwxrwx root/0            0 1979-12-31 16:00 ./bin/hello -> /nix/store/h92a9jd0lhhniv2q417hpwszd4jhys7q-hello-2.12.1/bin/hello
dr-xr-xr-x root/0            0 1979-12-31 16:00 ./nix/
dr-xr-xr-x root/0            0 1979-12-31 16:00 ./nix/store/
dr-xr-xr-x root/0            0 1979-12-31 16:00 ./nix/store/05zbwhz8a7i2v79r9j21pl6m6cj0xi8k-libunistring-1.1/
dr-xr-xr-x root/0            0 1979-12-31 16:00 ./nix/store/ayg5rhjhi9ic73hqw33mjqjxwv59ndym-xgcc-13.2.0-libgcc/
dr-xr-xr-x root/0            0 1979-12-31 16:00 ./nix/store/h92a9jd0lhhniv2q417hpwszd4jhys7q-hello-2.12.1/
dr-xr-xr-x root/0            0 1979-12-31 16:00 ./nix/store/m59xdgkgnjbk8kk6k6vbxmqnf82mk9s0-libidn2-2.3.4/
dr-xr-xr-x root/0            0 1979-12-31 16:00 ./nix/store/p3jshbwxiwifm1py0yq544fmdyy98j8a-glibc-2.38-27/
drwxr-xr-x root/0            0 1979-12-31 16:00 ./share/

Example 363. Importing an archive built with dockerTools.exportImage in Docker

We will use the same package from Example 362 and import it into Docker.

{ dockerTools, hello }:
dockerTools.exportImage {
  name = "hello";
  fromImage = dockerTools.buildLayeredImage {
    name = "hello";
    contents = [ hello ];
  };
}

Building and importing it into Docker:

$ nix-build
(output removed for clarity)
/nix/store/x6a5m7c6zdpqz1d8j7cnzpx9glzzvd2h-hello
$ docker image import /nix/store/x6a5m7c6zdpqz1d8j7cnzpx9glzzvd2h-hello
sha256:1d42dba415e9b298ea0decf6497fbce954de9b4fcb2984f91e307c8fedc1f52f
$ docker image ls
REPOSITORY                              TAG                IMAGE ID       CREATED         SIZE
<none>                                  <none>             1d42dba415e9   4 seconds ago   32.6MB

Example 364. Exploring output naming with dockerTools.exportImage

exportImage does not require a name attribute if fromImage is a derivation, which means that the following works:

{ dockerTools, hello }:
dockerTools.exportImage {
  fromImage = dockerTools.buildLayeredImage {
    name = "hello";
    contents = [ hello ];
  };
}

However, since dockerTools.buildLayeredImage’s output ends with .tar.gz, the output of exportImage will also end with .tar.gz, even though the archive created with exportImage is uncompressed:

$ nix-build
(output removed for clarity)
/nix/store/by3f40xvc4l6bkis74l0fj4zsy0djgkn-hello.tar.gz
$ file /nix/store/by3f40xvc4l6bkis74l0fj4zsy0djgkn-hello.tar.gz
/nix/store/by3f40xvc4l6bkis74l0fj4zsy0djgkn-hello.tar.gz: POSIX tar archive (GNU)

If the archive was actually compressed, the output of file would’ve mentioned that fact. Because of this, it may be important to set a proper name attribute when using exportImage with other functions from dockerTools.


Example 365. Using dockerTools.exportImage with a path as fromImage

It is possible to use a path as the value of the fromImage attribute when calling dockerTools.exportImage. However, when doing so, a name attribute MUST be specified, or you’ll encounter an error when evaluating the Nix code.

For this example, we’ll assume a Docker tarball image named image.tar.gz exists in the same directory where our package is defined:

{ dockerTools }:
dockerTools.exportImage {
  name = "filesystem.tar";
  fromImage = ./image.tar.gz;
}

Building this will give us the expected output:

$ nix-build
(output removed for clarity)
/nix/store/w13l8h3nlkg0zv56k7rj0ai0l2zlf7ss-filesystem.tar

If you don’t specify a name attribute, you’ll encounter an evaluation error and the package won’t build.


Environment Helpers

When building Docker images with Nix, you might also want to add certain files that are expected to be available globally by the software you’re packaging. Simple examples are the env utility in /usr/bin/env, or trusted root TLS/SSL certificates. Such files will most likely not be included if you’re building a Docker image from scratch with Nix, and they might also not be included if you’re starting from a Docker image that doesn’t include them. The helpers in this section are packages that provide some of these commonly-needed global files.

Most of these helpers are packages, which means you have to add them to the list of contents to be included in the image (this changes depending on the function you’re using to build the image). Example 366 and Example 367 show how to include these packages on dockerTools functions that build an image. For more details on how that works, see the documentation for the function you’re using.

usrBinEnv

This provides the env utility at /usr/bin/env. This is currently implemented by linking to the env binary from the coreutils package, but is considered an implementation detail that could change in the future.

binSh

This provides a /bin/sh link to the bash binary from the bash package. Because of this, it supports cases such as running a command interactively in a container (for example by running docker container run -it <image_name>).

caCertificates

This adds trusted root TLS/SSL certificates from the cacert package in multiple locations in an attempt to be compatible with binaries built for multiple Linux distributions. The locations currently used are:

  • /etc/ssl/certs/ca-bundle.crt

  • /etc/ssl/certs/ca-certificates.crt

  • /etc/pki/tls/certs/ca-bundle.crt

fakeNss

This is a re-export of the fakeNss package from Nixpkgs. See the section called “fakeNss”.

shadowSetup

This is a string containing a script that sets up files needed for shadow to work (using the shadow package from Nixpkgs), and alters PATH to make all its utilities available in the same script. It is intended to be used with other dockerTools functions in attributes that expect scripts. After the script in shadowSetup runs, you’ll then be able to add more commands that make use of the utilities in shadow, such as adding any extra users and/or groups. See Example 368 and Example 369 to better understand how to use it.

shadowSetup achieves a result similar to fakeNss, but only sets up a root user with different values for the home directory and the shell to use, in addition to setting up files for PAM and a login.defs(5) file.

Caution

Using both fakeNss and shadowSetup at the same time will either cause your build to break or produce unexpected results. Use either fakeNss or shadowSetup depending on your use case, but avoid using both.

Note

When used with buildLayeredImage or streamLayeredImage, you will have to set the enableFakechroot attribute to true, or else the script in shadowSetup won’t run properly. See Example 369.

Examples

Example 366. Using dockerTools’s environment helpers with buildImage

This example adds the binSh helper to a basic Docker image built with dockerTools.buildImage. This helper makes it possible to enter a shell inside the container. This is the buildImage equivalent of Example 367.

{ dockerTools, hello }:
dockerTools.buildImage {
  name = "env-helpers";
  tag = "latest";

  copyToRoot = [
    hello
    dockerTools.binSh
  ];
}

After building the image and loading it in Docker, we can create a container based on it and enter a shell inside the container. This is made possible by binSh.

$ nix-build
(some output removed for clarity)
/nix/store/2p0i3i04cgjlk71hsn7ll4kxaxxiv4qg-docker-image-env-helpers.tar.gz
$ docker image load -i /nix/store/2p0i3i04cgjlk71hsn7ll4kxaxxiv4qg-docker-image-env-helpers.tar.gz
(output removed for clarity)
$ docker container run --rm -it env-helpers:latest /bin/sh
sh-5.2# help
GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)
(rest of output removed for clarity)

Example 367. Using dockerTools’s environment helpers with buildLayeredImage

This example adds the binSh helper to a basic Docker image built with dockerTools.buildLayeredImage. This helper makes it possible to enter a shell inside the container. This is the buildLayeredImage equivalent of Example 366.

{ dockerTools, hello }:
dockerTools.buildLayeredImage {
  name = "env-helpers";
  tag = "latest";

  contents = [
    hello
    dockerTools.binSh
  ];

  config = {
    Cmd = [ "/bin/hello" ];
  };
}

After building the image and loading it in Docker, we can create a container based on it and enter a shell inside the container. This is made possible by binSh.

$ nix-build
(some output removed for clarity)
/nix/store/rpf47f4z5b9qr4db4ach9yr4b85hjhxq-env-helpers.tar.gz
$ docker image load -i /nix/store/rpf47f4z5b9qr4db4ach9yr4b85hjhxq-env-helpers.tar.gz
(output removed for clarity)
$ docker container run --rm -it env-helpers:latest /bin/sh
sh-5.2# help
GNU bash, version 5.2.21(1)-release (x86_64-pc-linux-gnu)
(rest of output removed for clarity)

Example 368. Using dockerTools.shadowSetup with dockerTools.buildImage

This is an example that shows how to use shadowSetup with dockerTools.buildImage. Note that the extra script in runAsRoot uses groupadd and useradd, which are binaries provided by the shadow package. These binaries are added to the PATH by the shadowSetup script, but only for the duration of runAsRoot.

{ dockerTools, hello }:
dockerTools.buildImage {
  name = "shadow-basic";
  tag = "latest";

  copyToRoot = [ hello ];

  runAsRoot = ''
    ${dockerTools.shadowSetup}
    groupadd -r hello
    useradd -r -g hello hello
    mkdir /data
    chown hello:hello /data
  '';

  config = {
    Cmd = [ "/bin/hello" ];
    WorkingDir = "/data";
  };
}

Example 369. Using dockerTools.shadowSetup with dockerTools.buildLayeredImage

It accomplishes the same thing as Example 368, but using buildLayeredImage instead.

Note that the extra script in fakeRootCommands uses groupadd and useradd, which are binaries provided by the shadow package. These binaries are added to the PATH by the shadowSetup script, but only for the duration of fakeRootCommands.

{ dockerTools, hello }:
dockerTools.buildLayeredImage {
  name = "shadow-basic";
  tag = "latest";

  contents = [ hello ];

  fakeRootCommands = ''
    ${dockerTools.shadowSetup}
    groupadd -r hello
    useradd -r -g hello hello
    mkdir /data
    chown hello:hello /data
  '';
  enableFakechroot = true;

  config = {
    Cmd = [ "/bin/hello" ];
    WorkingDir = "/data";
  };
}

buildNixShellImage

buildNixShellImage uses streamNixShellImage underneath to build a compressed Docker-compatible repository tarball of an image that sets up an environment similar to that of running nix-shell on a derivation. Basically, buildNixShellImage runs the script created by streamNixShellImage to save the compressed image in the Nix store.

buildNixShellImage supports the same options as streamNixShellImage, see streamNixShellImage for details.

Examples

Example 370. Building a Docker image with buildNixShellImage with the build environment for the hello package

This example shows how to build the hello package inside a Docker container built with buildNixShellImage. The Docker image generated will have a name like hello-<version>-env and tag latest. This example is the buildNixShellImage equivalent of Example 371.

{ dockerTools, hello }:
dockerTools.buildNixShellImage {
  drv = hello;
  tag = "latest";
}

The result of building this package is a .tar.gz file that can be loaded into Docker:

$ nix-build
(some output removed for clarity)
/nix/store/pkj1sgzaz31wl0pbvbg3yp5b3kxndqms-hello-2.12.1-env.tar.gz

$ docker image load -i /nix/store/pkj1sgzaz31wl0pbvbg3yp5b3kxndqms-hello-2.12.1-env.tar.gz
(some output removed for clarity)
Loaded image: hello-2.12.1-env:latest

After starting an interactive container, the derivation can be built by running buildDerivation, and the output can be executed as expected:

$ docker container run -it hello-2.12.1-env:latest
[nix-shell:~]$ buildDerivation
Running phase: unpackPhase
unpacking source archive /nix/store/pa10z4ngm0g83kx9mssrqzz30s84vq7k-hello-2.12.1.tar.gz
source root is hello-2.12.1
(some output removed for clarity)
Running phase: fixupPhase
shrinking RPATHs of ELF executables and libraries in /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1
shrinking /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1/bin/hello
checking for references to /build/ in /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1...
gzipping man pages under /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1/share/man/
patching script interpreter paths in /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1
stripping (with command strip and flags -S -p) in  /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1/bin

[nix-shell:~]$ $out/bin/hello
Hello, world!

streamNixShellImage

streamNixShellImage builds a script which, when run, will stream to stdout a Docker-compatible repository tarball of an image that sets up an environment similar to that of running nix-shell on a derivation. This means that streamNixShellImage does not output an image into the Nix store, but only a script that builds the image, saving on IO and disk/cache space, particularly with large images. See Example 371 to understand how to load in Docker the image generated by this script.

The environment set up by streamNixShellImage somewhat resembles the Nix sandbox typically used by nix-build, with a major difference being that access to the internet is allowed. It also behaves like an interactive nix-shell, running things like shellHook (see Example 373) and setting an interactive prompt. If the derivation is buildable (i.e. nix-build can be used on it), running buildDerivation in the container will build the derivation, with all its outputs being available in the correct /nix/store paths, pointed to by the respective environment variables (e.g. $out).

Caution

The environment in the image doesn’t match nix-shell or nix-build exactly, and this function is known not to work correctly for fixed-output derivations, content-addressed derivations, impure derivations and other special types of derivations.

Inputs

streamNixShellImage expects one argument with the following attributes:

drv (Attribute Set)

The derivation for which the environment in the image will be set up. Adding packages to the Docker image is possible by extending the list of nativeBuildInputs of this derivation. See Example 372 for how to do that. Similarly, you can extend the image initialization script by extending shellHook. Example 373 shows how to do that.

name (String; optional)

The name of the generated image.

Default value: the value of drv.name + "-env".

tag (String or Null; optional)

Tag of the generated image. If null, the hash of the nix derivation that builds the Docker image will be used as the tag.

Default value: null.

uid (Number; optional)

The user ID to run the container as. This can be seen as a nixbld build user.

Default value: 1000.

gid (Number; optional)

The group ID to run the container as. This can be seen as a nixbld build group.

Default value: 1000.

homeDirectory (String; optional)

The home directory of the user the container is running as.

Default value: /build.

shell (String; optional)

The path to the bash binary to use as the shell. This shell is started when running the image. This can be seen as an equivalent of the NIX_BUILD_SHELL environment variable for nix-shell(1).

Default value: the bash binary from the bash package.

command (String or Null; optional)

If specified, this command will be run in the environment of the derivation in an interactive shell. A call to exit will be added after the command if it is specified, so the shell will exit after it’s finished running. This can be seen as an equivalent of the --command option in nix-shell(1).

Default value: null.

run (String or Null; optional)

Similar to the command attribute, but runs the command in a non-interactive shell instead. A call to exit will be added after the command if it is specified, so the shell will exit after it’s finished running. This can be seen as an equivalent of the --run option in nix-shell(1).

Default value: null.

Examples

Example 371. Building a Docker image with streamNixShellImage with the build environment for the hello package

This example shows how to build the hello package inside a Docker container built with streamNixShellImage. The Docker image generated will have a name like hello-<version>-env and tag latest. This example is the streamNixShellImage equivalent of Example 370.

{ dockerTools, hello }:
dockerTools.streamNixShellImage {
  drv = hello;
  tag = "latest";
}

The result of building this package is a script. Running this script and piping it into docker image load gives you the same image that was built in Example 370.

$ nix-build
(some output removed for clarity)
/nix/store/8vhznpz2frqazxnd8pgdvf38jscdypax-stream-hello-2.12.1-env

$ /nix/store/8vhznpz2frqazxnd8pgdvf38jscdypax-stream-hello-2.12.1-env | docker image load
(some output removed for clarity)
Loaded image: hello-2.12.1-env:latest

After starting an interactive container, the derivation can be built by running buildDerivation, and the output can be executed as expected:

$ docker container run -it hello-2.12.1-env:latest
[nix-shell:~]$ buildDerivation
Running phase: unpackPhase
unpacking source archive /nix/store/pa10z4ngm0g83kx9mssrqzz30s84vq7k-hello-2.12.1.tar.gz
source root is hello-2.12.1
(some output removed for clarity)
Running phase: fixupPhase
shrinking RPATHs of ELF executables and libraries in /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1
shrinking /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1/bin/hello
checking for references to /build/ in /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1...
gzipping man pages under /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1/share/man/
patching script interpreter paths in /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1
stripping (with command strip and flags -S -p) in  /nix/store/f2vs29jibd7lwxyj35r9h87h6brgdysz-hello-2.12.1/bin

[nix-shell:~]$ $out/bin/hello
Hello, world!

Example 372. Adding extra packages to a Docker image built with streamNixShellImage

This example shows how to add extra packages to an image built with streamNixShellImage. In this case, we’ll add the cowsay package. The Docker image generated will have a name like hello-<version>-env and tag latest. This example uses Example 371 as a starting point.

{
  dockerTools,
  cowsay,
  hello,
}:
dockerTools.streamNixShellImage {
  tag = "latest";
  drv = hello.overrideAttrs (old: {
    nativeBuildInputs = old.nativeBuildInputs or [ ] ++ [ cowsay ];
  });
}

The result of building this package is a script which can be run and piped into docker image load to load the generated image.

$ nix-build
(some output removed for clarity)
/nix/store/h5abh0vljgzg381lna922gqknx6yc0v7-stream-hello-2.12.1-env

$ /nix/store/h5abh0vljgzg381lna922gqknx6yc0v7-stream-hello-2.12.1-env | docker image load
(some output removed for clarity)
Loaded image: hello-2.12.1-env:latest

After starting an interactive container, we can verify the extra package is available by running cowsay:

$ docker container run -it hello-2.12.1-env:latest
[nix-shell:~]$ cowsay "Hello, world!"
 _______________
< Hello, world! >
 ---------------
        \   ^__^
         \  (oo)\_______
            (__)\       )\/\
                ||----w |
                ||     ||

Example 373. Adding a shellHook to a Docker image built with streamNixShellImage

This example shows how to add a shellHook command to an image built with streamNixShellImage. In this case, we’ll simply output the string Hello, world!. The Docker image generated will have a name like hello-<version>-env and tag latest. This example uses Example 371 as a starting point.

{ dockerTools, hello }:
dockerTools.streamNixShellImage {
  tag = "latest";
  drv = hello.overrideAttrs (old: {
    shellHook = ''
      ${old.shellHook or ""}
      echo "Hello, world!"
    '';
  });
}

The result of building this package is a script which can be run and piped into docker image load to load the generated image.

$ nix-build
(some output removed for clarity)
/nix/store/iz4dhdvgzazl5vrgyz719iwjzjy6xlx1-stream-hello-2.12.1-env

$ /nix/store/iz4dhdvgzazl5vrgyz719iwjzjy6xlx1-stream-hello-2.12.1-env | docker image load
(some output removed for clarity)
Loaded image: hello-2.12.1-env:latest

After starting an interactive container, we can see the result of the shellHook:

$ docker container run -it hello-2.12.1-env:latest
Hello, world!

[nix-shell:~]$

pkgs.ociTools

pkgs.ociTools is a set of functions for creating runtime container bundles according to the OCI runtime specification v1.0.0. It makes no assumptions about the container runner you choose to use to run the created container.

The set of functions in pkgs.ociTools currently does not handle the OCI image specification.

At a high level, an OCI implementation would download an OCI Image then unpack that image into an OCI Runtime filesystem bundle. At this point, the OCI Runtime Bundle would be run by an OCI Runtime. pkgs.ociTools provides utilities to create OCI Runtime bundles.

buildContainer

This function creates an OCI runtime container (consisting of a config.json and a root filesystem directory) that runs a single command inside of it. The nix store of the container will contain all referenced dependencies of the given command.

This function has an assumption that the container will run on POSIX platforms, and sets configurations (such as the user running the process or certain mounts) according to this assumption. Because of this, a container built with buildContainer will not work on Windows or other non-POSIX platforms without modifications to the container configuration. These modifications aren’t supported by buildContainer.

For linux platforms, buildContainer also configures the following namespaces (see unshare(1)) to isolate the OCI container from the global namespace: PID, network, mount, IPC, and UTS.

Note that no user namespace is created, which means that you won’t be able to run the container unless you are the root user.

Inputs

buildContainer expects an argument with the following attributes:

args (List of String)

Specifies a set of arguments to run inside the container. Any packages referenced by args will be made available inside the container.

mounts (Attribute Set; optional)

Would specify additional mounts that the runtime must make available to the container.

Warning

As explained in issue #290879, this attribute is currently ignored.

Note

buildContainer includes a minimal set of necessary filesystems to be mounted into the container, and this set can’t be changed with the mounts attribute.

Default value: {}.

readonly (Boolean; optional)

If true, sets the container’s root filesystem as read-only.

Default value: false.

os DEPRECATED

Specifies the operating system on which the container filesystem is based. If specified, its value should follow the OCI Image Configuration Specification. According to the linked specification, all possible values for $GOOS in the Go docs should be valid, but will commonly be one of darwin or linux.

Default value: "linux".

arch DEPRECATED

Used to specify the architecture for which the binaries in the container filesystem have been compiled. If specified, its value should follow the OCI Image Configuration Specification. According to the linked specification, all possible values for $GOARCH in the Go docs should be valid, but will commonly be one of 386, amd64, arm, or arm64.

Default value: x86_64.

Examples

Example 374. Creating an OCI runtime container that runs bash

This example uses ociTools.buildContainer to create a simple container that runs bash.

{
  ociTools,
  lib,
  bash,
}:
ociTools.buildContainer {
  args = [ (lib.getExe bash) ];

  readonly = false;
}

As an example of how to run the container generated by this package, we’ll use runc to start the container. Any other tool that supports OCI containers could be used instead.

$ nix-build
(some output removed for clarity)
/nix/store/7f9hgx0arvhzp2a3qphp28rxbn748l25-join

$ cd /nix/store/7f9hgx0arvhzp2a3qphp28rxbn748l25-join
$ nix-shell -p runc
[nix-shell:/nix/store/7f9hgx0arvhzp2a3qphp28rxbn748l25-join]$ sudo runc run ocitools-example
help
GNU bash, version 5.2.26(1)-release (x86_64-pc-linux-gnu)
(some output removed for clarity)

pkgs.portableService

pkgs.portableService is a function to create Portable Services in a read-only, immutable, squashfs raw disk image. This lets you use Nix to build images which can be run on many recent Linux distributions.

Note

Portable services are supported starting with systemd 239 (released on 2018-06-22).

The generated image will contain the file system structure as required by the Portable Services specification, along with the packages given to portableService and all of their dependencies. When generated, the image will exist in the Nix store with the .raw file extension, as required by the specification. See Example 375 to understand how to use the output of portableService.

Inputs

portableService expects one argument with the following attributes:

pname (String)

The name of the portable service. The generated image will be named according to the template $pname_$version.raw, which is supported by the Portable Services specification.

version (String)

The version of the portable service. The generated image will be named according to the template $pname_$version.raw, which is supported by the Portable Services specification.

units (List of Attribute Set)

A list of derivations for systemd unit files. Each derivation must produce a single file, and must have a name that starts with the value of pname and ends with the suffix of the unit type (e.g. “.service”, “.socket”, “.timer”, and so on). See Example 375 to better understand this naming constraint.

description (String or Null; optional)

If specified, the value is added as PORTABLE_PRETTY_NAME to the /etc/os-release file in the generated image. This could be used to provide more information to anyone inspecting the image.

Default value: null.

homepage (String or Null; optional)

If specified, the value is added as HOME_URL to the /etc/os-release file in the generated image. This could be used to provide more information to anyone inspecting the image.

Default value: null.

symlinks (List of Attribute Set; optional)

A list of attribute sets in the format {object, symlink}. For each item in the list, portableService will create a symlink in the path specified by symlink (relative to the root of the image) that points to object.

All packages that object depends on and their dependencies are automatically copied into the image.

This can be used to create symlinks for applications that assume some files to exist globally (/etc/ssl or /bin/bash, for example). See Example 376 to understand how to do that.

Default value: [].

contents (List of Attribute Set; optional)

A list of additional derivations to be included as-is in the image. These derivations will be included directly in a /nix/store directory inside the image.

Default value: [].

squashfsTools (Attribute Set; optional)

Allows you to override the package that provides mksquashfs(1), which is used internally by portableService.

Default value: pkgs.squashfsTools.

squash-compression (String; optional)

Passed as the compression option to mksquashfs(1), which is used internally by portableService.

Default value: "xz -Xdict-size 100%".

squash-block-size (String; optional)

Passed as the block size option to mksquashfs(1), which is used internally by portableService.

Default value: "1M".

Examples

Example 375. Building a Portable Service image

The following example builds a Portable Service image with the hello package, along with a service unit that runs it.

{
  lib,
  writeText,
  portableService,
  hello,
}:
let
  hello-service = writeText "hello.service" ''
    [Unit]
    Description=Hello world service

    [Service]
    Type=oneshot
    ExecStart=${lib.getExe hello}
  '';
in
portableService {
  pname = "hello";
  inherit (hello) version;
  units = [ hello-service ];
}

After building the package, the generated image can be loaded into a system through portablectl(1):

$ nix-build
(some output removed for clarity)
/nix/store/8c20z1vh7z8w8dwagl8w87b45dn5k6iq-hello-img-2.12.1

$ portablectl attach /nix/store/8c20z1vh7z8w8dwagl8w87b45dn5k6iq-hello-img-2.12.1/hello_2.12.1.raw
Created directory /etc/systemd/system.attached.
Created directory /etc/systemd/system.attached/hello.service.d.
Written /etc/systemd/system.attached/hello.service.d/20-portable.conf.
Created symlink /etc/systemd/system.attached/hello.service.d/10-profile.conf → /usr/lib/systemd/portable/profile/default/service.conf.
Copied /etc/systemd/system.attached/hello.service.
Created symlink /etc/portables/hello_2.12.1.raw → /nix/store/8c20z1vh7z8w8dwagl8w87b45dn5k6iq-hello-img-2.12.1/hello_2.12.1.raw.

$ systemctl start hello
$ journalctl -u hello
Feb 28 22:39:16 hostname systemd[1]: Starting Hello world service...
Feb 28 22:39:16 hostname hello[102887]: Hello, world!
Feb 28 22:39:16 hostname systemd[1]: hello.service: Deactivated successfully.
Feb 28 22:39:16 hostname systemd[1]: Finished Hello world service.

$ portablectl detach hello_2.12.1
Removed /etc/systemd/system.attached/hello.service.
Removed /etc/systemd/system.attached/hello.service.d/10-profile.conf.
Removed /etc/systemd/system.attached/hello.service.d/20-portable.conf.
Removed /etc/systemd/system.attached/hello.service.d.
Removed /etc/portables/hello_2.12.1.raw.
Removed /etc/systemd/system.attached.

Example 376. Specifying symlinks when building a Portable Service image

Some services may expect files or directories to be available globally. An example is a service which expects all trusted SSL certificates to exist in a specific location by default.

To make things available globally, you must specify the symlinks attribute when using portableService. The following package builds on the package from Example 375 to make /etc/ssl available globally (this is only for illustrative purposes, because hello doesn’t use /etc/ssl).

{
  lib,
  writeText,
  portableService,
  hello,
  cacert,
}:
let
  hello-service = writeText "hello.service" ''
    [Unit]
    Description=Hello world service

    [Service]
    Type=oneshot
    ExecStart=${lib.getExe hello}
  '';
in
portableService {
  pname = "hello";
  inherit (hello) version;
  units = [ hello-service ];
  symlinks = [
    {
      object = "${cacert}/etc/ssl";
      symlink = "/etc/ssl";
    }
  ];
}

<nixpkgs/nixos/lib/make-disk-image.nix>

<nixpkgs/nixos/lib/make-disk-image.nix> is a function to create disk images in multiple formats: raw, QCOW2 (QEMU), QCOW2-Compressed (compressed version), VDI (VirtualBox), VPC (VirtualPC).

This function can create images in two ways:

  • using cptofs without any virtual machine to create a Nix store disk image,

  • using a virtual machine to create a full NixOS installation.

When testing early-boot or lifecycle parts of NixOS such as a bootloader or multiple generations, it is necessary to opt for a full NixOS system installation. Whereas for many web servers and applications, it is possible to work with a Nix store only disk image, which is faster to build.

NixOS tests also use this function when preparing the VM. The cptofs method is used when virtualisation.useBootLoader is false (the default). Otherwise the second method is used.

Features

For reference, read the function signature source code for documentation on arguments: https://github.com/NixOS/nixpkgs/blob/master/nixos/lib/make-disk-image.nix. Features are separated in various sections depending on if you opt for a Nix-store only image or a full NixOS image.

Common

  • arbitrary NixOS configuration

  • automatic or bound disk size: diskSize parameter, additionalSpace can be set when diskSize is auto to add a constant of disk space

  • multiple partition table layouts: EFI, legacy, legacy + GPT, hybrid, none through partitionTableType parameter

  • OVMF or EFI firmwares and variables templates can be customized

  • root filesystem fsType can be customized to whatever mkfs.${fsType} exists during operations

  • root filesystem label can be customized, defaults to nix-store if it’s a Nix store image, otherwise nixpkgs/nixos

  • arbitrary code can be executed after disk image was produced with postVM

  • the current nixpkgs can be realized as a channel in the disk image, which will change the hash of the image when the sources are updated

  • additional store paths can be provided through additionalPaths

Full NixOS image

  • arbitrary contents with permissions can be placed in the target filesystem using contents

  • a /etc/nixpkgs/nixos/configuration.nix can be provided through configFile

  • bootloaders are supported

  • EFI variables can be mutated during image production and the result is exposed in $out

  • boot partition size when partition table is efi or hybrid

On bit-to-bit reproducibility

Images are NOT deterministic. Please do not hesitate to try to fix this. Sources of non-determinism are (not exhaustive):

  • bootloader installation has timestamps

  • SQLite Nix store database contains registration times

  • /etc/shadow is in a non-deterministic order

A deterministic flag is available for best efforts determinism.

Usage

To produce a Nix-store only image:

let
  pkgs = import <nixpkgs> { };
  lib = pkgs.lib;
  make-disk-image = import <nixpkgs/nixos/lib/make-disk-image.nix>;
in
make-disk-image {
  inherit pkgs lib;
  config = { };
  additionalPaths = [ ];
  format = "qcow2";
  onlyNixStore = true;
  partitionTableType = "none";
  installBootLoader = false;
  touchEFIVars = false;
  diskSize = "auto";
  additionalSpace = "0M"; # Defaults to 512M.
  copyChannel = false;
}

Some arguments can be left out, they are shown explicitly for the sake of the example.

Building this derivation will provide a QCOW2 disk image containing only the Nix store and its registration information.

To produce a NixOS installation image disk with UEFI and bootloader installed:

let
  pkgs = import <nixpkgs> { };
  lib = pkgs.lib;
  make-disk-image = import <nixpkgs/nixos/lib/make-disk-image.nix>;
  evalConfig = import <nixpkgs/nixos/lib/eval-config.nix>;
in
make-disk-image {
  inherit pkgs lib;
  inherit
    (evalConfig {
      modules = [
        {
          fileSystems."/" = {
            device = "/dev/vda";
            fsType = "ext4";
            autoFormat = true;
          };
          boot.grub.device = "/dev/vda";
        }
      ];
    })
    config
    ;
  format = "qcow2";
  onlyNixStore = false;
  partitionTableType = "legacy+gpt";
  installBootLoader = true;
  touchEFIVars = true;
  diskSize = "auto";
  additionalSpace = "0M"; # Defaults to 512M.
  copyChannel = false;
  memSize = 2048; # Qemu VM memory size in MiB (1024*1024 bytes). Defaults to 1024M.
}

pkgs.mkBinaryCache

pkgs.mkBinaryCache is a function for creating Nix flat-file binary caches. Such a cache exists as a directory on disk, and can be used as a Nix substituter by passing --substituter file:///path/to/cache to Nix commands.

Nix packages are most commonly shared between machines using HTTP, SSH, or S3, but a flat-file binary cache can still be useful in some situations. For example, you can copy it directly to another machine, or make it available on a network file system. It can also be a convenient way to make some Nix packages available inside a container via bind-mounting.

mkBinaryCache expects an argument with the rootPaths attribute. rootPaths must be a list of derivations. The transitive closure of these derivations’ outputs will be copied into the cache.

Optional arguments

compression ("none" or "xz" or "zstd"; optional)

The compression algorithm to use.

Default value: zstd.

Note

This function is meant for advanced use cases. The more idiomatic way to work with flat-file binary caches is via the nix-copy-closure command. You may also want to consider dockerTools for your containerization needs.

Example 377. Copying a package and its closure to another machine with mkBinaryCache

The following derivation will construct a flat-file binary cache containing the closure of hello.

{ mkBinaryCache, hello }: mkBinaryCache { rootPaths = [ hello ]; }

Build the cache on a machine. Note that the command still builds the exact nix package above, but adds some boilerplate to build it directly from an expression.

$ nix-build -E 'let pkgs = import <nixpkgs> {}; in pkgs.callPackage ({ mkBinaryCache, hello }: mkBinaryCache { rootPaths = [hello]; }) {}'
/nix/store/azf7xay5xxdnia4h9fyjiv59wsjdxl0g-binary-cache

Copy the resulting directory to another machine, which we’ll call host2:

$ scp result host2:/tmp/hello-cache

At this point, the cache can be used as a substituter when building derivations on host2:

$ nix-build -A hello '<nixpkgs>' \
  --option require-sigs false \
  --option trusted-substituters file:///tmp/hello-cache \
  --option substituters file:///tmp/hello-cache
/nix/store/zhl06z4lrfrkw5rp0hnjjfrgsclzvxpm-hello-2.12.1

Hooks reference

Nixpkgs has several hook packages that augment the stdenv phases.

The stdenv built-in hooks are documented in the section called “Package setup hooks”.

Autoconf

The autoreconfHook derivation adds autoreconfPhase, which runs autoreconf, libtoolize and automake, essentially preparing the configure script in autotools-based builds. Most autotools-based packages come with the configure script pre-generated, but this hook is necessary for a few packages and when you need to patch the package’s configure scripts.

Automake

Adds the share/aclocal subdirectory of each build input to the ACLOCAL_PATH environment variable.

autoPatchcilHook

This is a special setup hook which helps in packaging .NET assemblies/programs in that it automatically tries to find missing shared library dependencies of .NET assemblies based on the given buildInputs and nativeBuildInputs.

As the hook needs information for the host where the package will be run on, there’s a required environment variable called autoPatchcilRuntimeId which should be filled in with the RID (Runtime Identifier) of the machine where the output will be run on. If you’re using buildDotnetModule, it will fall back to dotnetRuntimeIds (which is set to lib.singleton (if runtimeId != null then runtimeId else systemToDotnetRid stdenvNoCC.hostPlatform.system)) for you if not provided.

In certain situations you may want to run the main command (autoPatchcil) of the setup hook on a file or a set of directories instead of unconditionally patching all outputs. This can be done by setting the dontAutoPatchcil environment variable to a non-empty value.

By default, autoPatchcil will fail as soon as any .NET assembly requires a dependency which cannot be resolved via the given build inputs. In some situations you might prefer to just leave missing dependencies unpatched and continue to patch the rest. This can be achieved by setting the autoPatchcilIgnoreMissingDeps environment variable to a non-empty value. autoPatchcilIgnoreMissingDeps can be set to a list like autoPatchcilIgnoreMissingDeps = [ "libcuda.so.1" "libcudart.so.1" ]; or to [ "*" ] to ignore all missing dependencies.

The autoPatchcil command requires the --rid command line flag, informing the RID (Runtime Identifier) it should assume the assemblies will be executed on, and also recognizes a --no-recurse command line flag, which prevents it from recursing into subdirectories.

Note

Since, unlike most native binaries, .NET assemblies are compiled once to run on any platform, many assemblies may have PInvoke stubs for libraries that might not be available on the platform that the package will effectively run on. A few examples are assemblies that call native Windows APIs through PInvoke targeting kernel32, gdi32, user32, shell32 or ntdll.

autoPatchcil does its best to ignore dependencies from other platforms by checking the requested file extensions, however not all PInvoke stubs provide an extension so in those cases it will be necessary to list those in autoPatchcilIgnoreMissingDeps manually.

autoPatchelfHook

This is a special setup hook which helps in packaging proprietary software in that it automatically tries to find missing shared library dependencies of ELF files based on the given buildInputs and nativeBuildInputs.

You can also specify a runtimeDependencies variable which lists dependencies to be unconditionally added to the rpath of all executables. This is useful for programs that use dlopen to load libraries at runtime.

In certain situations you may want to run the main command (autoPatchelf) of the setup hook on a file or a set of directories instead of unconditionally patching all outputs. This can be done by setting the dontAutoPatchelf environment variable to a non-empty value.

By default autoPatchelf will fail as soon as any ELF file requires a dependency which cannot be resolved via the given build inputs. In some situations you might prefer to just leave missing dependencies unpatched and continue to patch the rest. This can be achieved by setting the autoPatchelfIgnoreMissingDeps environment variable to a non-empty value. autoPatchelfIgnoreMissingDeps can be set to a list like autoPatchelfIgnoreMissingDeps = [ "libcuda.so.1" "libcudart.so.1" ]; or to [ "*" ] to ignore all missing dependencies.

The autoPatchelf command also recognizes a --no-recurse command line flag, which prevents it from recursing into subdirectories.

aws-c-common

This hook exposes its own CMake modules by setting CMAKE_MODULE_PATH through the cmakeFlags variable to the nonstandard $out/lib/cmake directory, as a workaround for an upstream bug.

bmake

bmake is the portable variant of NetBSD make utility.

In Nixpkgs, bmake comes with a hook that overrides the default build, check, install and dist phases.

breakpointHook

This hook makes a build pause instead of stopping when a failure occurs. It prevents Nix from cleaning up the build environment immediately and allows the user to attach to the build environment. Upon a build error, it will print instructions that can be used to enter the environment for debugging. The breakpointHook is only available on Linux. To use it, add breakpointHook to nativeBuildInputs in the package to be inspected.

{ nativeBuildInputs = [ breakpointHook ]; }

When a build failure occurs, an instruction will be printed showing how to attach to the build sandbox.

Note

Caution with remote builds

For remote builds, the printed instructions need to be run on the remote machine, as the build sandbox is only accessible on the machine running the builds. Remote builds can be turned off by setting --option builders '' for nix-build or --builders '' for nix build. :::

CERNLIB

This hook sets the CERN, CERN_LEVEL, and CERN_ROOT environment variables. They are part of CERNLIB’s build system and are needed for some programs to compile correctly.

cmake

Overrides the default configure phase to run the CMake command.

By default, we use the Make generator of CMake. But when Ninja is also available as a nativeBuildInput, this setup hook will detect that and use the ninja generator.

Dependencies are added automatically to CMAKE_PREFIX_PATH so that packages are correctly detected by CMake. Some additional flags are passed in to give similar behavior to configure-based packages.

By default, parallel building is enabled as CMake supports parallel building almost everywhere.

You can disable this hook’s behavior by setting configurePhase to a custom value, or by setting dontUseCmakeConfigure.

Variables controlling CMake

CMake Exclusive Variables

cmakeFlags

Controls the flags passed to cmake setup during configure phase.

cmakeBuildDir

Directory where CMake will put intermediate files.

Setting this can be useful for debugging multiple CMake builds while in the same source directory, for example, when building for different platforms. Different values for each build will prevent build artifacts from interfering with each other. This setting has no tangible effect when running the build in a sandboxed derivation.

The default value is build.

cmakeBuildType

Build type of cmake output.

Internally populates the CMAKE_BUILD_TYPE cmake flag.

The default value is Release.

dontUseCmakeConfigure

When set to true, don’t use the predefined cmakeConfigurePhase.

Controlling CTest invocation

By default tests are run by make in checkPhase or by ninja if ninja is available in nativeBuildInputs. Makefile and Ninja generators produce the test target, which invokes ctest under the hood. This makes passing additional arguments to ctest difficult, so it’s possible to invoke it directly in checkPhase by adding ctestCheckHook to nativeCheckInputs.

CTest Variables

disabledTests

Allows to disable running a list of tests. Note that regular expressions are not supported by disabledTests, but it can be combined with --exclude-regex option.

ctestFlags

Additional options passed to ctest together with checkFlags.

desktop-file-utils

This setup hook removes the MIME cache (located at $out/share/applications/mimeinfo.cache) in the preFixupPhase.

This hook is necessary because mimeinfo.cache can be created when a package uses desktop-file-utils, resulting in collisions if multiple packages are installed that contain this file (as in #48295).

gdk-pixbuf

Exports GDK_PIXBUF_MODULE_FILE environment variable to the builder. Add librsvg package to buildInputs to get svg support. See also the setup hook description in GNOME platform docs.

GHC

Creates a temporary package database and registers every Haskell build input in it (TODO: how?).

GNOME platform

Hooks related to GNOME platform and related libraries like GLib, GTK and GStreamer are described in the section called “GNOME”.

haredo

This hook uses the haredo command runner to build, check, and install the package. It overrides buildPhase, checkPhase, and installPhase by default.

The hook builds its targets in parallel if enableParallelBuilding is set to true.

buildPhase

This phase attempts to build the default target.

Targets can be explicitly set by adding a string to the haredoBuildTargets list.

This behavior can be disabled by setting dontUseHaredoBuild to true.

checkPhase

This phase searches for the check.do or test.do targets, running them if they exist.

Targets can be explicitly set by adding a string to the haredoCheckTargets list.

This behavior can be disabled by setting dontUseHaredoCheck to true.

installPhase

This phase attempts to build the install.do target, if it exists.

Targets can be explicitly set by adding a string to the haredoInstallTargets list.

This behavior can be disabled by setting dontUseHaredoInstall to true.

installShellFiles

This hook adds helpers that install artifacts like executable files, manpages and shell completions.

It exposes the following functions that can be used from your postInstall hook:

installBin

The installBin function takes one or more paths to files to install as executable files.

This function will place them into outputBin.

Example Usage

{
  nativeBuildInputs = [ installShellFiles ];

  # Sometimes the file has an undesirable name. It should be renamed before
  # being installed via installBin
  postInstall = ''
    mv a.out delmar
    installBin foobar delmar
  '';
}

installManPage

The installManPage function takes one or more paths to manpages to install.

The manpages must have a section suffix, and may optionally be compressed (with .gz suffix). This function will place them into the correct share/man/man<section>/ directory in outputMan.

Example Usage

{
  nativeBuildInputs = [ installShellFiles ];

  # Sometimes the manpage file has an undesirable name; e.g., it conflicts with
  # another software with an equal name. To install it with a different name,
  # the installed name must be provided before the path to the file.
  #
  # Below install a manpage "foobar.1" from the source file "./foobar.1", and
  # also installs the manpage "fromsea.3" from the source file "./delmar.3".
  postInstall = ''
    installManPage \
        foobar.1 \
        --name fromsea.3 delmar.3
  '';
}

The manpage may be the result of a piped input (e.g. <(cmd)), in which case the name must be provided before the pipe with the --name flag.

{
  nativeBuildInputs = [ installShellFiles ];

  postInstall = ''
    installManPage --name foobar.1 <($out/bin/foobar --manpage)
  '';
}

If no parsing of arguments is desired, pass -- to opt-out of all subsequent arguments.

{
  nativeBuildInputs = [ installShellFiles ];

  # Installs a manpage from a file called "--name"
  postInstall = ''
    installManPage -- --name
  '';
}

installShellCompletion

The installShellCompletion function takes one or more paths to shell completion files.

By default it will autodetect the shell type from the completion file extension, but you may also specify it by passing one of --bash, --fish, --zsh, or --nushell. These flags apply to all paths listed after them (up until another shell flag is given). Each path may also have a custom installation name provided by providing a flag --name NAME before the path. If this flag is not provided, zsh completions will be renamed automatically such that foobar.zsh becomes _foobar. A root name may be provided for all paths using the flag --cmd NAME; this synthesizes the appropriate name depending on the shell (e.g. --cmd foo will synthesize the name foo.bash for bash and _foo for zsh).

Example Usage

{
  nativeBuildInputs = [ installShellFiles ];
  postInstall = ''
    # explicit behavior
    installShellCompletion --bash --name foobar.bash share/completions.bash
    installShellCompletion --fish --name foobar.fish share/completions.fish
    installShellCompletion --nushell --name foobar share/completions.nu
    installShellCompletion --zsh --name _foobar share/completions.zsh
    # implicit behavior
    installShellCompletion share/completions/foobar.{bash,fish,zsh,nu}
  '';
}

The path may also be the result of process substitution (e.g. <(cmd)), in which case the shell and name must be provided (see below).

If the destination shell completion file is not actually present or consists of zero bytes after calling installShellCompletion this is treated as a build failure. In particular, if completion files are not vendored but are generated by running an executable, this is likely to fail in cross compilation scenarios. The result will be a zero byte completion file and hence a build failure. To prevent this, guard the completion generation commands.

Example Usage

{
  nativeBuildInputs = [ installShellFiles ];
  postInstall = lib.optionalString (stdenv.buildPlatform.canExecute stdenv.hostPlatform) ''
    # using process substitution
    installShellCompletion --cmd foobar \
      --bash <($out/bin/foobar --bash-completion) \
      --fish <($out/bin/foobar --fish-completion) \
      --nushell <($out/bin/foobar --nushell-completion) \
      --zsh <($out/bin/foobar --zsh-completion)
  '';
}

installFonts

This hook installs common font formats to the proper location. In its default state, the hook automatically handles ttf, ttc, otf, bdf, and psf. Given a webfont output, woff and woff2 formats will be installed under this output.

The automatic behavior of the hook can be disabled by setting the dontInstallFonts variable to true.

Additionally, it exposes the installFont function that can be used from your postInstall hook, to install additional formats:

installFont

The installFont function takes two arguments, a file extension to move (without a preceding dot), and the install location.

Example Usage

{
  nativeBuildInputs = [ installFonts ];

  postInstall = ''
    installFont svg $out/share/fonts/svg
  '';
}

julec.hook

Jule is an effective programming language designed to build efficient, fast, reliable and safe software while maintaining simplicity.

In Nixpkgs, jule.hook overrides the default build, check and install phases.

Example code snippet

{
  julec,
  clangStdenv,
}:

clangStdenv.mkDerivation (finalAttrs: {
  # ...

  nativeBuildInputs = [ julec.hook ];

  # Customize filenames if needed
  JULE_SRC_DIR = "./src";
  JULE_OUT_DIR = "./bin";
  JULE_OUT_NAME = "hello-jule";
  JULE_TEST_DIR = "./tests";
  JULE_TEST_OUT_DIR = "./test-bin";
  JULE_TEST_OUT_NAME = "hello-jule-test";

  # ...
})

Variables controlling julec.hook

JULE_SRC_DIR

Specifies the source directory containing main.jule. Default is ./src.

JULE_OUT_DIR

Specifies the output directory for the compiled binary. Default is ./bin.

JULE_OUT_NAME

Specifies the name of the compiled binary. Default is output.

JULE_TEST_DIR

Specifies the directory containing test files. Default is the value of JULE_SRC_DIR.

JULE_TEST_OUT_DIR

Specifies the output directory for compiled test binaries. Default is the value of JULE_OUT_DIR.

JULE_TEST_OUT_NAME

Specifies the name of the compiled test binary. Default is the value of JULE_OUT_NAME with -test suffix.

dontUseJulecBuild

When set to true, doesn’t use the predefined julecBuildHook. Default is false.

dontUseJulecCheck

When set to true, doesn’t use the predefined julecCheckHook. Default is false.

dontUseJulecInstall

When set to true, doesn’t use the predefined julecInstallHook. Default is false.

just

This setup hook attempts to use the just command runner to build, check, and install the package. The hook overrides buildPhase, checkPhase, and installPhase by default.

The justFlags variable can be set to a list of strings to add additional flags passed to all invocations of just.

buildPhase

This phase attempts to invoke just with the default recipe.

This behavior can be disabled by setting dontUseJustBuild to true.

checkPhase

This phase attempts to invoke the just test recipe, if it is available. This can be overridden by setting checkTarget to a string.

This behavior can be disabled by setting dontUseJustCheck to true.

installPhase

This phase attempts to invoke the just install recipe.

This behavior can be disabled by setting dontUseJustInstall to true.

libglycin

Glycin is a library for sandboxed and extendable image loading.

For most applications using it, individual image formats are loaded through binaries provided by glycin-loaders. The paths of these loaders must be injected into the environment, e.g. using wrapGAppsHook. libglycin.setupHook will do that.

Additionally, for Rust projects glycin Rust crate itself requires a patch to become self-contained. libglycin.patchVendorHook will do that. This is not needed for projects using the ELF library from libglycin package.

Example code snippet

{
  lib,
  rustPlatform,
  libglycin,
  glycin-loaders,
  wrapGAppsHook4,
}:

rustPlatform.buildRustPackage {
  # ...

  cargoHash = "...";

  nativeBuildInputs = [
    wrapGAppsHook4
    libglycin.patchVendorHook
  ];

  buildInputs = [
    libglycin.setupHook
    glycin-loaders
  ];

  # ...
}

Variables controlling glycin-loaders

glycinCargoDepsPath

Path to a directory containing the glycin crate to patch. Defaults to the crate directory created by cargoSetupHook, or ./vendor/.

dontWrapGlycinLoaders

Disable adding the Glycin loaders path XDG_DATA_DIRS with wrapGAppsHook.

libiconv, libintl

A few libraries automatically add to NIX_LDFLAGS their library, making their symbols automatically available to the linker. This includes libiconv and libintl (gettext). This is done to provide compatibility between GNU Linux, where libiconv and libintl are bundled in, and other systems where that might not be the case. Sometimes, this behavior is not desired. To disable this behavior, set dontAddExtraLibs.

libxml2

Adds every file named catalog.xml found under the xml/dtd and xml/xsl subdirectories of each build input to the XML_CATALOG_FILES environment variable.

Meson

Meson is an open source meta build system meant to be fast and user-friendly.

In Nixpkgs, meson comes with a setup hook that overrides the configure, check, and install phases.

Being a meta build system, meson needs an accompanying backend. In the context of Nixpkgs, the typical companion backend is Ninja, that provides a setup hook registering ninja-based build and install phases.

Variables controlling Meson

Meson Exclusive Variables

mesonFlags

Controls the flags passed to meson setup during configure phase.

mesonBuildDir

Directory where Meson will put intermediate files.

Setting this can be useful for debugging multiple Meson builds while in the same source directory, for example, when building for different platforms. Different values for each build will prevent build artifacts from interfering with each other. This setting has no tangible effect when running the build in a sandboxed derivation.

The default value is build.

mesonWrapMode

Which value is passed as -Dwrap_mode=. In Nixpkgs, the default value is nodownload, so that no subproject will be downloaded (since network access is already disabled during deployment in Nixpkgs).

Note: Meson allows pre-population of subprojects that would otherwise be downloaded.

mesonBuildType

Which value is passed as --buildtype to meson setup during configure phase. In Nixpkgs, the default value is plain.

mesonAutoFeatures

Which value is passed as -Dauto_features= to meson setup during configure phase. In Nixpkgs, the default value is enabled, meaning that every feature declared as “auto” by the meson scripts will be enabled.

mesonCheckFlags

Controls the flags passed to meson test during check phase.

mesonInstallFlags

Controls the flags passed to meson install during install phase.

mesonInstallTags

A list of installation tags passed to Meson’s commandline option --tags during install phase.

Note: mesonInstallTags should be a list of strings that will be converted to a comma-separated string that is recognized to --tags. Example: mesonInstallTags = [ "emulator" "assembler" ]; will be converted to --tags emulator,assembler.

dontUseMesonConfigure

When set to true, don’t use the predefined mesonConfigurePhase.

dontUseMesonCheck

When set to true, don’t use the predefined mesonCheckPhase.

dontUseMesonInstall

When set to true, don’t use the predefined mesonInstallPhase.

Honored variables

The following variables commonly used by stdenv.mkDerivation are honored by Meson setup hook.

  • prefixKey

  • enableParallelBuilding

  • enableParallelChecking

mpiCheckPhaseHook

This hook can be used to setup a check phase that requires running a MPI application. It detects the present MPI implementation type and exports the necessary environment variables to use mpirun and mpiexec in a Nix sandbox.

Example:

{ mpiCheckPhaseHook, mpi, ... }:
{
  # ...

  nativeCheckInputs = [
    openssh
    mpiCheckPhaseHook
  ];
}

ninja

Overrides the build, install, and check phase to run ninja instead of make. You can disable this behavior with dontUseNinjaBuild, dontUseNinjaInstall, and dontUseNinjaCheck, respectively. Parallel building is enabled by default in Ninja.

Note that if the Meson setup hook is also active, Ninja’s install and check phases will be disabled in favor of Meson’s.

nodejsInstallExecutables

Hook for wrapping Node.js executables. Primarily created for a multi-language environment.

Examples

Example 378

Variables controlling nodejsInstallExecutables

nodejsInstallExecutables Exclusive Variables

makeWrapperArgs

Flags to pass to the call to makeWrapper. To avoid double-wrapping, this flag can also be accessed in Bash.

stdenv.mkDerivation (finalAttrs: {
  #...
  dontWrapGApps = true;

  postInstall = ''
    makeWrapperArgs+=("''${gappsWrapperArgs[@]}")
  '';
  #...
})

nodejsInstallManuals

Detects manuals in Node.js packages, and attempts to install them in standard locations. This detection is done by inspecting the package.json of the project and finding any entries with type man.

There are no ways currently to configure this hook.

Examples

Example 378

npmHooks.npmBuildHook

Hook for building packages that use npm. Can be used in multi-language environments.

Examples

Example 378. Using npmHooks
{
  stdenv,
  fetchFromGitHub,
  fetchNpmDeps,
  npmHooks,
  nodejsInstallExecutables,
  nodejsInstallManuals,
  nodejs,
}:
stdenv.mkDerivation (finalAttrs: {
  pname = "some-npm-project";
  version = "1.0";

  src = fetchFromGitHub {
    owner = "JohnNpm";
    repo = "SomeProject";
    tag = finalAttrs.version;
    hash = "...";
  };

  strictDeps = true;

  nativeBuildInputs = [
    nodejs
    nodejsInstallExecutables
    nodejsInstallManuals
    npmHooks.npmConfigHook
    npmHooks.npmBuildHook
    npmHooks.npmInstallHook
  ];

  npmBuildScript = "build";

  npmBuildFlags = [
    "--prod"
  ];

  npmFlags = [
    "--ignore-scripts"
  ];

  npmDeps = fetchNpmDeps {
    inherit (finalAttrs) src;
    hash = "...";
  };

  makeWrapperArgs = [
    "--set"
    "NODE_ENV"
    "production"
  ];

  meta = {
    description = "npm project";
  };
})

Variables controlling npmBuildHook

npmBuildHook Exclusive Variables

npmBuildScript

Controls the script ran to build the npm package within the package.json file. Required to be set, usually to build, but can vary between packages.

npmBuildFlags

Controls the arguments to the npm run $npmBuildScript command.

dontNpmBuild

Disables npmBuildHook when enabled

Honored Variables

The following variables are honored by the npmBuildHook.

npmHooks.npmConfigHook

Hook for configuring packages that use npm. Primarily made for a multi-language environment.

Examples

Example 378

Variables controlling npmConfigHook

npmConfigHook Exclusive Variables

npmDeps

Derivation that contains the npm package dependencies. Usually built with fetchNpmDeps. This attribute is required or the hook will abort the build.

makeCacheWritable

Whether to make the dependency cache writable prior to installing the dependencies. Don’t set this unless npm tries to write to the cache directory.

npmInstallFlags

Flags to pass to the npm ci call for installing the dependencies to the build environment. Defaults to --ignore-scripts, which cannot be removed. This does not control anything with the npmInstallHook.

npmRebuildFlags

Flags to pass to the npm rebuild command after the dependencies are installed to the environment.

Honored Variables

The following variables are honored by the npmConfigHook.

npmHooks.npmInstallHook

Hook to install node_modules for npm packages. Does not create wrappers for executable npm projects Primarily made for a multi-language environment.

Examples

Example 378

Variables controlling npmInstallHook

npmInstallHook Exclusive Variables

dontNpmPrune

Whether to run npm prune on the node_modules or not. Defaults to true.

npmInstallFlags

Flags to pass to the npm prune call for the node_modules of the package. Defaults to --omit=dev --no-save which cannot be modified.

dontNpmInstall

Controls whether npmInstallHook is enabled or not. Defaults to true, so the hook will run.

Honored Variables

The following variables are honored by the npmInstallHook.

patchRcPath hooks

These hooks provide shell-specific utilities (with the same name as the hook) to patch shell scripts meant to be sourced by software users.

The typical usage is to patch initialisation or rc scripts inside $out/bin or $out/etc. Such scripts, when being sourced, would insert the binary locations of certain commands into PATH, modify other environment variables or run a series of start-up commands. When shipped from the upstream, they sometimes use commands that might not be available in the environment they are getting sourced in.

The compatible shells for each hook are:

  • patchRcPathBash: Bash, ksh, zsh and other shells supporting the Bash-like parameter expansions.

  • patchRcPathCsh: Csh scripts, such as those targeting tcsh.

  • patchRcPathFish: Fish scripts.

  • patchRcPathPosix: POSIX-conformant shells supporting the limited parameter expansions specified by the POSIX standard. The current implementation uses the parameter expansion ${foo-} only.

For each supported shell, it modifies the script with a PATH prefix that is later removed when the script ends. It allows nested patching, which guarantees that a patched script may source another patched script.

Syntax to apply the utility to a script:

patchRcPath<shell> <file> <PATH-prefix>

Example usage:

Given a package foo containing an init script this-foo.fish that depends on coreutils, man and which, patch the init script for users to source without having the above dependencies in their PATH:

{
  lib,
  stdenv,
  patchRcPathFish,
}:
stdenv.mkDerivation {

  # ...

  nativeBuildInputs = [ patchRcPathFish ];

  postFixup = ''
    patchRcPathFish $out/bin/this-foo.fish ${
      lib.makeBinPath [
        coreutils
        man
        which
      ]
    }
  '';
}

Note

patchRcPathCsh and patchRcPathPosix implementation depends on sed to do the string processing. The others are in vanilla shell and have no third-party dependencies.

Perl

Adds the lib/site_perl subdirectory of each build input to the PERL5LIB environment variable. For instance, if buildInputs contains Perl, then the lib/site_perl subdirectory of each input is added to the PERL5LIB environment variable.

pkg-config

Adds the lib/pkgconfig and share/pkgconfig subdirectories of each build input to the PKG_CONFIG_PATH environment variable.

postgresqlTestHook

This hook starts a PostgreSQL server during the checkPhase. Example:

{
  stdenv,
  postgresql,
  postgresqlTestHook,
}:
stdenv.mkDerivation {

  # ...

  nativeCheckInputs = [
    postgresql
    postgresqlTestHook
  ];
}

If you use a custom checkPhase, remember to add the runHook calls:

checkPhase ''
  runHook preCheck

  # ... your tests

  runHook postCheck
''

Variables

The hook logic will read a number of variables and set them to a default value if unset or empty.

Exported variables:

  • PGDATA: location of server files.

  • PGHOST: location of UNIX domain socket directory; the default host in a connection string.

  • PGUSER: user to create / log in with, default: test_user.

  • PGDATABASE: database name, default: test_db.

Bash-only variables:

  • postgresqlTestUserOptions: SQL options to use when creating the $PGUSER role, default: "LOGIN". Example: "LOGIN SUPERUSER"

  • postgresqlTestSetupSQL: SQL commands to run as database administrator after startup, default: statements that create $PGUSER and $PGDATABASE.

  • postgresqlTestSetupCommands: bash commands to run after database start, defaults to running $postgresqlTestSetupSQL as database administrator.

  • postgresqlEnableTCP: set to 1 to enable TCP listening. Flaky; not recommended.

  • postgresqlStartCommands: defaults to pg_ctl start.

  • postgresqlExtraSettings: Additional configuration to add to postgresql.conf

Hooks

A number of additional hooks are run in postgresqlTestHook

  • postgresqlTestSetupPost: run after postgresql has been set up.

TCP and the Nix sandbox

postgresqlEnableTCP relies on network sandboxing, which is not available on macOS and some custom Nix installations, resulting in flaky tests. For this reason, it is disabled by default.

The preferred solution is to make the test suite use a UNIX domain socket connection. This is the default behavior when no host connection parameter is provided. Some test suites hardcode a value for host though, so a patch may be required. If you can upstream the patch, you can make host default to the PGHOST environment variable when set. Otherwise, you can patch it locally to omit the host connection string parameter altogether.

Note

The error libpq: failed (could not receive data from server: Connection refused is generally an indication that the test suite is trying to connect through TCP.

Premake

This setup hook attempts to configure the package using the Premake build configuration system. It overrides the configurePhase by default, if none exists.

The Premakefile to use can be specified by setting premakefile in the derivation.

The flags passed to Premake can be configured by adding strings to the premakeFlags list.

Python

Adds the python.sitePackages subdirectory (i.e. lib/pythonX.Y/site-packages) of each build input to the PYTHONPATH environment variable.

scons

Overrides the build, install, and check phases. This uses the scons build system as a replacement for make. scons does not provide a configure phase, so everything is managed at build and install time.

cargo-tauri.hook

Tauri is a framework for building smaller, faster, and more secure desktop applications with a web frontend.

In Nixpkgs, cargo-tauri.hook overrides the default build and install phases.

Example code snippet

{
  lib,
  stdenv,
  rustPlatform,
  fetchNpmDeps,
  cargo-tauri,
  glib-networking,
  nodejs,
  npmHooks,
  openssl,
  pkg-config,
  webkitgtk_4_1,
  wrapGAppsHook4,
}:

rustPlatform.buildRustPackage (finalAttrs: {
  # ...

  cargoHash = "...";

  # Assuming our app's frontend uses `npm` as a package manager
  npmDeps = fetchNpmDeps {
    name = "${finalAttrs.pname}-${finalAttrs.version}-npm-deps";
    inherit (finalAttrs) src;
    hash = "...";
  };

  nativeBuildInputs = [
    # Pull in our main hook
    cargo-tauri.hook

    # Setup npm
    nodejs
    npmHooks.npmConfigHook

    # Make sure we can find our libraries
    pkg-config
  ]
  ++ lib.optionals stdenv.hostPlatform.isLinux [ wrapGAppsHook4 ];

  buildInputs = lib.optionals stdenv.hostPlatform.isLinux [
    glib-networking # Most Tauri apps need networking
    openssl
    webkitgtk_4_1
  ];

  # Set our Tauri source directory
  cargoRoot = "src-tauri";
  # And make sure we build there too
  buildAndTestSubdir = finalAttrs.cargoRoot;

  # ...
})

Variables controlling cargo-tauri

Tauri Exclusive Variables

tauriBuildFlags

Controls the flags passed to cargo tauri build.

tauriBundleType

The bundle type to build.

dontTauriBuild

Disables using tauriBuildHook.

dontTauriFixup

Disables the tauriFixupHook pre fixup phase.

dontTauriInstall

Disables using tauriInstallPostBuildHook and tauriInstallHook.

Honored Variables

Along with those found in the section called “buildRustPackage: Compiling Rust applications with Cargo”, the following variables used by cargoBuildHook and cargoInstallHook are honored by the cargo-tauri setup hook.

  • buildAndTestSubdir

  • cargoBuildType

  • cargoBuildNoDefaultFeatures

  • cargoBuildFeatures

teTeX / TeX Live

Adds the share/texmf-nix subdirectory of each build input to the TEXINPUTS environment variable.

udevCheckHook

The udevCheckHook derivation adds udevCheckPhase to the preInstallCheckHooks, which finds all udev rules in all outputs and verifies them using udevadm verify --resolve-names=never --no-style. It should be used in any package that has udev rules outputs to ensure the rules are and remain valid.

The hook runs in installCheckPhase, requiring doInstallCheck is enabled for the hook to take effect:

{
  lib,
  stdenv,
  udevCheckHook,
  # ...
}:

stdenv.mkDerivation (finalAttrs: {
  # ...

  nativeInstallCheckInputs = [ udevCheckHook ];
  doInstallCheck = true;

  # ...
})

Note that for buildPythonPackage and buildPythonApplication, doInstallCheck is enabled by default.

All outputs are scanned for their /{etc,lib}/udev/rules.d paths. If no rule output is found, the hook is basically a no-op.

The udevCheckHook adds a dependency on systemdMinimal. It is internally guarded behind hostPlatform supporting udev and buildPlatform being able to execute udevadm. The hook does not need explicit platform checks in the places where it is used.

The hook can be disabled using dontUdevCheck, which is necessary if you want to run some different task in installCheckPhase on a package with broken udev rule outputs.

unzip

This setup hook will allow you to unzip .zip files specified in $src. There are many similar packages like unrar, undmg, etc.

validatePkgConfig

The validatePkgConfig hook validates all pkg-config (.pc) files in a package. This helps catch some common errors in pkg-config files, such as undefined variables.

versionCheckHook

This hook adds a versionCheckPhase to the preInstallCheckHooks that runs the main program of the derivation with a --help or --version argument, and checks that the ${version} string is found in that output. If this check fails then the whole build will fail. (A softer option is testers.testVersion.)

You use it like this:

{
  lib,
  stdenv,
  versionCheckHook,
  # ...
}:

stdenv.mkDerivation (finalAttrs: {
  # ...

  nativeInstallCheckInputs = [ versionCheckHook ];
  doInstallCheck = true;

  # ...
})

Note that for buildPythonPackage and buildPythonApplication, doInstallCheck is enabled by default.

It does so in a clean environment (using env --ignore-environment), and it checks for the ${version} string in both the stdout and the stderr of the command. It will report to you in the build log the output it received and it will fail the build if it failed to find ${version}.

The variables that this phase control are:

  • dontVersionCheck: Disable adding this hook to the preInstallCheckHooks. Useful if you do want to load the bash functions of the hook, but run them differently.

  • versionCheckProgram: The full path to the program that should print the ${version} string. Defaults to using the first non-empty value $binary out of ${NIX_MAIN_PROGRAM} and ${pname}, in that order, to build roughly ${placeholder "out"}/bin/$binary. ${NIX_MAIN_PROGRAM}'s value comes from meta.mainProgram, and does not normally need to be set explicitly. When setting versionCheckProgram, using $out directly won’t work, as environment variables from this variable are not expanded by the hook. Hence using placeholder "out" is unavoidable.

  • versionCheckProgramArg: The argument that needs to be passed to versionCheckProgram. If undefined the hook tries first --version and then --help. Examples: version, -V, -v.

  • versionCheckKeepEnvironment: A list of environment variables to keep and pass to the command. Only those variables should be added to this list that are actually required for the version command to work. If it is not feasible to explicitly list all these environment variables you can set this parameter to the special value "*" to disable the --ignore-environment flag and thus keep all environment variables.

  • preVersionCheck: A hook to run before the check is done.

  • postVersionCheck: A hook to run after the check is done.

This check assumes the executable is hermetic. If environment variables such as PATH or HOME are required for the program to function, then testers.testVersion is currently the better alternative.

wafHook

Waf is a Python-based software building system.

In Nixpkgs, wafHook overrides the default configure, build, and install phases.

Variables controlling wafHook

wafHook Exclusive Variables

The variables below are exclusive of wafHook.

wafPath

Location of the waf tool. It defaults to ./waf, to honor software projects that include it directly inside their source trees.

If the file pointed by wafPath doesn’t exist, then waf provided by Nixpkgs will be used.

wafFlags

Controls the flags passed to waf tool during build and install phases. For settings specific to build or install phases, use wafBuildFlags or wafInstallFlags, respectively.

dontUseWafConfigure

When set to true, don’t use the predefined wafConfigurePhase.

dontUseWafBuild

When set to true, don’t use the predefined wafBuildPhase.

dontUseWafInstall

When set to true, don’t use the predefined wafInstallPhase.

Similar variables

The following variables are similar to their stdenv.mkDerivation counterparts.

wafHook Variablestdenv.mkDerivation Counterpart
wafConfigureFlagsconfigureFlags
wafConfigureTargetsconfigureTargets
wafBuildFlagsbuildFlags
wafBuildTargetsbuildTargets
wafInstallFlagsinstallFlags
wafInstallTargetsinstallTargets

Honored variables

The following variables commonly used by stdenv.mkDerivation are honored by wafHook.

  • prefixKey

  • enableParallelBuilding

  • enableParallelInstalling

Zig

Zig is a general-purpose programming language and toolchain for maintaining robust, optimal and reusable software.

In Nixpkgs, zig overrides the default build, check and install phases.

Example code snippet

{
  lib,
  stdenv,
  zig,
}:

stdenv.mkDerivation {
  # . . .

  nativeBuildInputs = [ zig ];

  zigBuildFlags = [ "-Dman-pages=true" ];

  dontUseZigCheck = true;

  # . . .
}

Variables controlling zig

zig Exclusive Variables

The variables below are exclusive to zig.

dontUseZigConfigure

Disables using zigConfigurePhase.

dontUseZigBuild

Disables using zigBuildPhase.

dontUseZigCheck

Disables using zigCheckPhase.

dontUseZigInstall

Disables using zigInstallPhase.

dontSetZigDefaultFlags

Disables using a set of default flags when performing zig builds.

Similar variables

The following variables are similar to their stdenv.mkDerivation counterparts.

zig Variablestdenv.mkDerivation Counterpart
zigBuildFlagsbuildFlags
zigCheckFlagscheckFlags
zigInstallFlagsinstallFlags

Variables honored by zig

The following variables commonly used by stdenv.mkDerivation are honored by zig.

  • prefixKey

  • dontAddPrefix

xcbuildHook

Overrides the build and install phases to run the “xcbuild” command. This hook is needed when a project only comes with build files for the XCode build system. You can disable this behavior by setting buildPhase and configurePhase to a custom value. xcbuildFlags controls flags passed only to xcbuild.

xfce4-dev-tools

This setup hook attempts to run xdt-autogen in xdtAutogenPhase, which is part of preConfigurePhases.

This behavior can be disabled by setting dontUseXdtAutogenPhase to true.

Languages and frameworks

The standard build environment makes it easy to build typical Autotools-based packages with very little code. Any other kind of package can be accommodated by overriding the appropriate phases of stdenv. However, there are specialised functions in Nixpkgs to easily build packages for other programming languages, such as Perl or Haskell. These are described in this chapter.

Each supported language or software ecosystem has its own package set named <language or ecosystem>Packages, which can be explored in various ways:

  • Search on search.nixos.org

    For example, search for haskellPackages or rubyPackages.

  • Navigate attribute sets with nix repl.

    This technique is generally useful to inspect Nix language data structures.

    Example 379. Navigate Java compiler variants in javaPackages with nix repl
    $ nix repl -f '<nixpkgs>' -I nixpkgs=channel:nixpkgs-unstable
    nix-repl> javaPackages.<tab>
    javaPackages.compiler               javaPackages.openjfx15              javaPackages.openjfx21              javaPackages.recurseForDerivations
    javaPackages.jogl_2_4_0             javaPackages.openjfx17              javaPackages.openjfx25
    javaPackages.mavenfod               javaPackages.openjfx19              javaPackages.override
    javaPackages.openjfx11              javaPackages.openjfx20              javaPackages.overrideDerivation
    

  • List all derivations on the command line with nix-env --query.

    nix-env is the only convenient way to do that, as it will skip attributes that fail assertions, such as when a package is marked as broken, rather than failing the entire evaluation.

    Example 380. List all Python packages in Nixpkgs

    The following command lists all derivations names with their attribute path from the latest Nixpkgs rolling release (nixpkgs-unstable).

    $ nix-env -qaP -f '<nixpkgs>' -A pythonPackages -I nixpkgs=channel:nixpkgs-unstable
    
    pythonPackages.avahi                                                  avahi-0.8
    pythonPackages.boost                                                  boost-1.81.0
    pythonPackages.caffe                                                  caffe-1.0
    pythonPackages.caffeWithCuda                                          caffe-1.0
    pythonPackages.cbeams                                                 cbeams-1.0.3
    …
    

Agda

How to use Agda

Agda is available as the agda package.

The agda package installs an Agda-wrapper, which calls agda with --library-file set to a generated library-file within the nix store, this means your library-file in $HOME/.agda/libraries will be ignored. By default the agda package installs Agda with no libraries, i.e. the generated library-file is empty. To use Agda with libraries, the agda.withPackages function can be used. This function either takes:

  • A list of packages,

  • or a function which returns a list of packages when given the agdaPackages attribute set,

  • or an attribute set containing a list of packages and a GHC derivation for compilation (see below).

  • or an attribute set containing a function which returns a list of packages when given the agdaPackages attribute set and a GHC derivation for compilation (see below).

For example, suppose we wanted a version of Agda which has access to the standard library. This can be obtained with the expressions:

agda.withPackages [ agdaPackages.standard-library ]

or

agda.withPackages (p: [ p.standard-library ])

or can be called as in the Compiling Agda section.

If you want to use a different version of a library (for instance a development version) override the src attribute of the package to point to your local repository

agda.withPackages (p: [
  (p.standard-library.overrideAttrs (oldAttrs: {
    version = "local version";
    src = /path/to/local/repo/agda-stdlib;
  }))
])

You can also reference a GitHub repository

agda.withPackages (p: [
  (p.standard-library.overrideAttrs (oldAttrs: {
    version = "1.5";
    src = fetchFromGitHub {
      repo = "agda-stdlib";
      owner = "agda";
      rev = "v1.5";
      hash = "sha256-nEyxYGSWIDNJqBfGpRDLiOAnlHJKEKAOMnIaqfVZzJk=";
    };
  }))
])

If you want to use a library not added to Nixpkgs, you can add a dependency to a local library by calling agdaPackages.mkDerivation.

agda.withPackages (p: [
  (p.mkDerivation {
    pname = "your-agda-lib";
    version = "1.0.0";
    src = /path/to/your-agda-lib;
  })
])

Again you can reference GitHub

agda.withPackages (p: [
  (p.mkDerivation {
    pname = "your-agda-lib";
    version = "1.0.0";
    src = fetchFromGitHub {
      repo = "repo";
      owner = "owner";
      version = "...";
      rev = "...";
      hash = "...";
    };
  })
])

See Building Agda Packages for more information on mkDerivation.

Agda will not by default use these libraries. To tell Agda to use a library we have some options:

  • Call agda with the library flag:

    $ agda -l standard-library -i . MyFile.agda
    
  • Write a my-library.agda-lib file for the project you are working on which may look like:

    name: my-library
    include: .
    depend: standard-library
    
  • Create the file ~/.agda/defaults and add any libraries you want to use by default.

More information can be found in the official Agda documentation on library management.

Compiling Agda

Agda modules can be compiled using the GHC backend with the --compile flag. A version of ghc with ieee754 is made available to the Agda program via the --with-compiler flag. This can be overridden by a different version of ghc as follows:

agda.withPackages {
  pkgs = [
    # ...
  ];
  ghc = haskell.compiler.ghcHEAD;
}

To install Agda without GHC, use ghc = null;.

Writing Agda packages

To write a nix derivation for an Agda library, first check that the library has a (single) *.agda-lib file.

A derivation can then be written using agdaPackages.mkDerivation. This has similar arguments to stdenv.mkDerivation with the following additions:

  • libraryName should be the name that appears in the *.agda-lib file, defaulting to pname.

  • libraryFile should be the file name of the *.agda-lib file, defaulting to ${libraryName}.agda-lib.

Here is an example default.nix

{
  nixpkgs ? <nixpkgs>,
}:
with (import nixpkgs { });
agdaPackages.mkDerivation {
  version = "1.0";
  pname = "my-agda-lib";
  src = ./.;
  buildInputs = [ agdaPackages.standard-library ];
}

Building Agda packages

The default build phase for agdaPackages.mkDerivation runs agda --build-library. If something else is needed to build the package (e.g. make) then the buildPhase should be overridden. Additionally, a preBuild or configurePhase can be used if there are steps that need to be done prior to checking the library. agda and the Agda libraries contained in buildInputs are made available during the build phase.

Installing Agda packages

The default install phase copies Agda source files, Agda interface files (*.agdai) and *.agda-lib files to the output directory. This can be overridden.

By default, Agda sources are files ending on .agda, or literate Agda files ending on .lagda, .lagda.tex, .lagda.org, .lagda.md, .lagda.rst. The list of recognised Agda source extensions can be extended by setting the extraExtensions config variable.

Maintaining the Agda package set on Nixpkgs

We are aiming at providing all common Agda libraries as packages on nixpkgs, and keeping them up to date. Contributions and maintenance help is always appreciated, but the maintenance effort is typically low since the Agda ecosystem is quite small.

The nixpkgs Agda package set tries to take up a role similar to that of Stackage in the Haskell world. It is a curated set of libraries that:

  1. Always work together.

  2. Are as up-to-date as possible.

While the Haskell ecosystem is huge, and Stackage is highly automated, the Agda package set is small and can (still) be maintained by hand.

Adding Agda packages to Nixpkgs

To add an Agda package to nixpkgs, the derivation should be written to pkgs/development/libraries/agda/${library-name}/default.nix and an entry should be added to pkgs/top-level/agda-packages.nix. Here it is called in a scope with access to all other Agda libraries, so the derivation could look like:

{
  mkDerivation,
  standard-library,
  fetchFromGitHub,
}:

mkDerivation {
  pname = "my-library";
  version = "1.0";
  src = <...>;
  buildInputs = [ standard-library ];
  meta = <...>;
}

You can look at other files under pkgs/development/libraries/agda/ for more inspiration.

Note that the derivation function is called with mkDerivation set to agdaPackages.mkDerivation, therefore you could use a similar set as in your default.nix from Writing Agda Packages with agdaPackages.mkDerivation replaced with mkDerivation.

Here is an example skeleton derivation for iowa-stdlib:

mkDerivation {
  version = "1.5.0";
  pname = "iowa-stdlib";

  src = <...>;

  libraryFile = "";
  libraryName = "IAL-1.3";

  buildPhase = ''
    runHook preBuild

    patchShebangs find-deps.sh
    make

    runHook postBuild
  '';
}

This library has a file called .agda-lib, and so we give an empty string to libraryFile as nothing precedes .agda-lib in the filename. This file contains name: IAL-1.3, and so we let libraryName = "IAL-1.3". This library does not use an Everything.agda file and instead has a Makefile, so there is no need to set everythingFile and we set a custom buildPhase.

When writing an Agda package, it is essential to make sure that no .agda-lib file gets added to the store as a single file (for example by using writeText). This causes Agda to think that the nix store is a Agda library and it will attempt to write to it whenever it typechecks something. See https://github.com/agda/agda/issues/4613.

In the pull request adding this library, you can test whether it builds correctly by writing in a comment:

@ofborg build agdaPackages.my-library

Maintaining Agda packages

As mentioned before, the aim is to have a compatible, and up-to-date package set. These two conditions sometimes exclude each other: For example, if we update agdaPackages.standard-library because there was an upstream release, this will typically break many reverse dependencies, i.e. downstream Agda libraries that depend on the standard library. In nixpkgs we are typically among the first to notice this, since we have build tests in place to check this.

In a pull request updating e.g. the standard library, you should write the following comment:

@ofborg build agdaPackages.standard-library.passthru.tests

This will build all reverse dependencies of the standard library, for example agdaPackages.agda-categories.

In some cases it is useful to build all Agda packages. This can be done with the following Github comment:

@ofborg build agda.passthru.tests.allPackages

Sometimes, the builds of the reverse dependencies fail because they have not yet been updated and released. You should drop the maintainers a quick issue notifying them of the breakage, citing the build error (which you can get from the ofborg logs). If you are motivated, you might even send a pull request that fixes it. Usually, the maintainers will answer within a week or two with a new release. Bumping the version of that reverse dependency should be a further commit on your PR.

In the rare case that a new release is not to be expected within an acceptable time, mark the broken package as broken by setting meta.broken = true;. This will exclude it from the build test. It can be added later when it is fixed, and does not hinder the advancement of the whole package set in the meantime.

Android

The Android build environment provides three major features and a number of supporting features.

Using androidenv with Android Studio

Use the android-studio-full attribute for a very complete Android SDK, including system images:

{ buildInputs = [ android-studio-full ]; }

This is identical to:

{ buildInputs = [ androidStudioPackages.stable.full ]; }

Alternatively, you can pass composeAndroidPackages to the withSdk passthrough:

{
  buildInputs = [
    (android-studio.withSdk (androidenv.composeAndroidPackages { includeNDK = true; }).androidsdk)
  ];
}

These will export ANDROID_HOME and ANDROID_NDK_ROOT to the SDK and NDK directories in the specified Android build environment.

Deploying an Android SDK installation with plugins

Alternatively, you can deploy the SDK separately with a desired set of plugins, or subsets of an SDK.

with import <nixpkgs> { };

let
  androidComposition = androidenv.composeAndroidPackages {
    platformVersions = [
      "34"
      "35"
      "latest"
    ];
    systemImageTypes = [ "google_apis_playstore" ];
    abiVersions = [
      "armeabi-v7a"
      "arm64-v8a"
    ];
    includeNDK = true;
    includeExtras = [ "extras;google;auto" ];
  };
in
androidComposition.androidsdk

The above function invocation states that we want an Android SDK with the above specified plugin versions. By default, most plugins are disabled. Notable exceptions are the tools, platform-tools and build-tools sub packages.

The following parameters are supported:

  • cmdLineToolsVersion specifies the version of the cmdline-tools package to use. It defaults to the latest.

  • toolsVersion, specifies the version of the tools package. Notice tools is obsolete, and currently only 26.1.1 is available, so there’s not a lot of options here, however, you can set it as null if you don’t want it. It defaults to the latest.

  • platformToolsVersion specifies the version of the platform-tools plugin. It defaults to the latest.

  • buildToolsVersions specifies the versions of the build-tools plugins to use. It defaults to the latest.

  • includeEmulator specifies whether to deploy the emulator package (false by default). When enabled, the version of the emulator to deploy can be specified by setting the emulatorVersion parameter. If set to "if-supported", it will deploy the emulator if it’s supported by the system.

  • includeCmake specifies whether CMake should be included. It defaults to true on x86-64 and Darwin platforms, and also supports "if-supported".

  • cmakeVersions specifies which CMake versions should be deployed. It defaults to the latest.

  • includeNDK specifies that the Android NDK bundle should be included. Defaults to false though can be set to true or "if-supported".

  • ndkVersions specifies the NDK versions that we want to use. These are linked under the ndk directory of the SDK root, and the first is linked under the ndk-bundle directory. It defaults to the latest.

  • ndkVersion is equivalent to specifying one entry in ndkVersions, and ndkVersions overrides this parameter if provided.

  • includeExtras is an array of identifier strings referring to arbitrary add-on packages that should be installed. Note that extras may not be compatible with all platforms (for example, the Google TV head unit, which does not have an aarch64-linux compile).

  • platformVersions specifies which platform SDK versions should be included. It defaults to including only the latest API level, though you can add more.

  • numLatestPlatformVersions specifies how many of the latest API levels to include, if you are using the default for platformVersions. It defaults to 1, though you can increase this to, for example, 5 to get the last 5 years of Android API packages.

  • minPlatformVersion and maxPlatformVersion take priority over platformVersions if both are provided. Note that maxPlatformVersion always defaults to the latest Android SDK platform version, allowing you to specify minPlatformVersion to describe the minimum SDK version your Android composition supports.

For each platform version that has been specified, we can apply the following options:

  • includeSystemImages specifies whether a system image for each platform SDK should be included.

  • includeSources specifies whether the sources for each SDK version should be included.

  • useGoogleAPIs specifies that for each selected platform version the Google API should be included.

  • useGoogleTVAddOns specifies that for each selected platform version the Google TV add-on should be included.

For each requested system image we can specify the following options:

  • systemImageTypes specifies what kind of system images should be included. Defaults to: default.

  • abiVersions specifies what kind of ABI version of each system image should be included. Defaults to armeabi-v7a and arm64-v8a.

Most of the function arguments have reasonable default settings, preferring the latest versions of tools when possible. You can additionally specify “latest” for any plugin version that you do not care about, and just want the latest of.

You can specify license names:

  • extraLicenses is a list of license names. You can get these names from repo.json or querypackages.sh licenses. The SDK license (android-sdk-license) is accepted for you if you set accept_license to true. If you are doing something like working with preview SDKs, you will want to add android-sdk-preview-license or whichever license applies here.

Additionally, you can override the repositories that composeAndroidPackages will pull from:

  • repoJson specifies a path to a generated repo.json file. You can generate this by running generate.sh, which in turn will call into mkrepo.rb.

  • repoXmls is an attribute set containing paths to repo XML files. If specified, it takes priority over repoJson, and will trigger a local build writing out a repo.json to the Nix store based on the given repository XMLs. Note that this uses import-from-derivation.

{
  repoXmls = {
    packages = [ ./xml/repository2-1.xml ];
    images = [
      ./xml/android-sys-img2-1.xml
      ./xml/android-tv-sys-img2-1.xml
      ./xml/android-wear-sys-img2-1.xml
      ./xml/android-wear-cn-sys-img2-1.xml
      ./xml/google_apis-sys-img2-1.xml
      ./xml/google_apis_playstore-sys-img2-1.xml
    ];
    addons = [ ./xml/addon2-1.xml ];
  };
}

When building the above expression with:

$ nix-build

The Android SDK gets deployed with all desired plugin versions.

We can also deploy subsets of the Android SDK. For example, to only the platform-tools package, you can evaluate the following expression:

with import <nixpkgs> { };

let
  androidComposition = androidenv.composeAndroidPackages {
    # ...
  };
in
androidComposition.platform-tools

Using predefined Android package compositions

In addition to composing an Android package set manually, it is also possible to use a predefined composition that contains a fairly complete set of Android packages:

The following Nix expression can be used to deploy the entire SDK:

with import <nixpkgs> { };

androidenv.androidPkgs.androidsdk

It is also possible to use one plugin only:

with import <nixpkgs> { };

androidenv.androidPkgs.platform-tools

Spawning emulator instances

For testing purposes, it can also be quite convenient to automatically generate scripts that spawn emulator instances with all desired configuration settings.

An emulator spawn script can be configured by invoking the emulateApp {} function:

with import <nixpkgs> { };

androidenv.emulateApp {
  name = "emulate-MyAndroidApp";
  platformVersion = "28";
  abiVersion = "x86"; # armeabi-v7a, mips, x86_64
  systemImageType = "google_apis_playstore";
}

Additional flags may be applied to the Android SDK’s emulator through the runtime environment variable $NIX_ANDROID_EMULATOR_FLAGS.

It is also possible to specify an APK to deploy inside the emulator and the package and activity names to launch it:

with import <nixpkgs> { };

androidenv.emulateApp {
  name = "emulate-MyAndroidApp";
  platformVersion = "24";
  abiVersion = "armeabi-v7a"; # mips, x86, x86_64
  systemImageType = "default";
  app = ./MyApp.apk;
  package = "MyApp";
  activity = "MainActivity";
}

In addition to prebuilt APKs, you can also bind the APK parameter to a buildApp {} function invocation shown in the previous example.

Notes on environment variables in Android projects

  • ANDROID_HOME should point to the Android SDK. In your Nix expressions, this should be ${androidComposition.androidsdk}/libexec/android-sdk. Note that ANDROID_SDK_ROOT is deprecated, but if you rely on tools that need it, you can export it too.

  • ANDROID_NDK_ROOT should point to the Android NDK, if you’re doing NDK development. In your Nix expressions, this should be ${ANDROID_HOME}/ndk-bundle.

If you are running the Android Gradle plugin, you need to export GRADLE_OPTS to override aapt2 to point to the aapt2 binary in the Nix store as well, or use a FHS environment so the packaged aapt2 can run. If you don’t want to use a FHS environment, something like this should work:

let
  buildToolsVersion = "30.0.3";

  # Use buildToolsVersion when you define androidComposition
  androidComposition = <...>;
in
pkgs.mkShell rec {
  ANDROID_HOME = "${androidComposition.androidsdk}/libexec/android-sdk";
  ANDROID_NDK_ROOT = "${ANDROID_HOME}/ndk-bundle";

  # Use the same buildToolsVersion here
  GRADLE_OPTS = "-Dorg.gradle.project.android.aapt2FromMavenOverride=${ANDROID_HOME}/build-tools/${buildToolsVersion}/aapt2";
}

If you are using cmake, you need to add it to PATH in a shell hook or FHS env profile. The path is suffixed with a build number, but properly prefixed with the version. So, something like this should suffice:

let
  cmakeVersion = "3.10.2";

  # Use cmakeVersion when you define androidComposition
  androidComposition = <...>;
in
pkgs.mkShell rec {
  ANDROID_HOME = "${androidComposition.androidsdk}/libexec/android-sdk";
  ANDROID_NDK_ROOT = "${ANDROID_HOME}/ndk-bundle";

  # Use the same cmakeVersion here
  shellHook = ''
    export PATH="$(echo "$ANDROID_HOME/cmake/${cmakeVersion}".*/bin):$PATH"
  '';
}

Note that running Android Studio with ANDROID_HOME set will automatically write a local.properties file with sdk.dir set to $ANDROID_HOME if one does not already exist. If you are using the NDK as well, you may have to add ndk.dir to this file.

An example shell.nix that does all this for you is provided in examples/shell.nix. This shell.nix includes a shell hook that overwrites local.properties with the correct sdk.dir and ndk.dir values. This will ensure that the SDK and NDK directories will both be correct when you run Android Studio inside nix-shell.

Notes on improving build.gradle compatibility

Ensure that your buildToolsVersion and ndkVersion match what is declared in androidenv. If you are using cmake, make sure its declared version is correct too.

Otherwise, you may get cryptic errors from aapt2 and the Android Gradle plugin warning that it cannot install the build tools because the SDK directory is not writable.

android {
    buildToolsVersion "30.0.3"
    ndkVersion = "22.0.7026061"
    externalNativeBuild {
        cmake {
            version "3.10.2"
        }
    }
}

Querying the available versions of each plugin

All androidenv packages are available on search.nixos.org. Note that aarch64-linux compatibility is currently spotty, though x86_64-linux and aarch64-darwin are well supported. This is because Google’s repository definitions mark some packages for “all” architectures that are really only for x86_64 or aarch64.

Updating the generated expressions

repo.json is generated from XML files that the Android Studio package manager uses. To update the expressions run the update.sh script that is stored in the pkgs/development/mobile/androidenv/ subdirectory:

./update.sh

This is run automatically by the nixpkgs update script.

Building an Android application with Ant

In addition to the SDK, it is also possible to build an Ant-based Android project and automatically deploy all the Android plugins that a project requires. Most newer Android projects use Gradle, and this is included for historical purposes.

with import <nixpkgs> { };

androidenv.buildApp {
  name = "MyAndroidApp";
  src = ./myappsources;
  release = true;

  # If release is set to true, you need to specify the following parameters
  keyStore = ./keystore;
  keyAlias = "myfirstapp";
  keyStorePassword = "mykeystore";
  keyAliasPassword = "myfirstapp";

  # Any Android SDK parameters that install all the relevant plugins that a
  # build requires
  platformVersions = [ "24" ];

  # When we include the NDK, then ndk-build is invoked before Ant gets invoked
  includeNDK = true;
}

Aside from the app-specific build parameters (name, src, release and keystore parameters), the buildApp {} function supports all the function parameters that the SDK composition function (the function shown in the previous section) supports.

This build function is particularly useful when it is desired to use Hydra: the Nix-based continuous integration solution to build Android apps. An Android APK gets exposed as a build product and can be installed on any Android device with a web browser by navigating to the build result page.

Astal

Astal is a collection of building blocks for creating custom desktop shells.

Bundling

Bundling an Astal application is done using the ags tool. You can use it like this:

ags.bundle {
  pname = "hyprpanel";
  version = "1.0.0";

  src = fetchFromGitHub {
    #...
  };

  # change your entry file (default is `app.ts`)
  entry = "app.ts";

  dependencies = [
    # list here astal modules that your package depends on
    # `astal3`, `astal4` and `astal.io` are automatically included
    astal.apps
    astal.battery
    astal.bluetooth

    # you can also list here other runtime dependencies
    hypridle
    hyprpicker
    hyprsunset
  ];

  # GTK 4 support is opt-in
  enableGtk4 = true;

  meta = {
    #...
  };
}

You can also pass all other arguments that are supported by stdenv.mkDerivation.

BEAM Languages (Erlang, Elixir & LFE)

Introduction

In this document and related Nix expressions, we use the term, BEAM, to describe the environment. BEAM is the name of the Erlang Virtual Machine and, as far as we’re concerned, from a packaging perspective, all languages that run on the BEAM are interchangeable. That which varies, like the build system, is transparent to users of any given BEAM package, so we make no distinction.

Available versions and deprecations schedule

Erlang OTP

Nixpkgs follows upstream Erlang in their support lifecycle and keeps up to the last 3 released versions of Erlang available. Due to upstream and NixOS release timings, this may mean removal of the oldest release prior to upstream fully dropping support.

Elixir

Nixpkgs follows the official elixir deprecation schedule and keeps up to the last 5 released versions of Elixir available.

Structure

All BEAM-related expressions are available via top-level package sets. It is recommended to work with a single package set to ensure consistent versions.

  • beamPackages - default OTP version

  • beamMinimalPackages - default OTP version, without wxwidgets, which saves ~1GB in closure size

There are also OTP version specific package sets, e.g. for OTP 28:

  • beam28Packages

  • beamMinimal28Packages

Inside each package set are:

  • erlang itself (version comes from package set)

  • interpreters: elixir (multiple versions, e.g. elixir_1_18) and lfe

  • packages: rebar3, hex, etc

  • builders: mixRelease, buildRebar3, etc

  • hooks: for composing builders and packages

To use a non-default Elixir it’s important to keep the rest of the package set consistent, so it’s recommended to use .extend. This ensures that builders like mixRelease, fetchMixDeps, and buildMix all pick up the overridden Elixir:

let
  beamPackages = beam27Packages.extend (self: super: { elixir = self.elixir_1_18; });
in
beamPackages.mixRelease {
  # ...
}

Build Tools

Rebar3

We provide a version of Rebar3, under beamPackages.rebar3. We also provide a helper to fetch Rebar3 dependencies from a lockfile under beamPackages.fetchRebar3Deps.

We also provide a version on Rebar3 with plugins included, under beamPackages.rebar3WithPlugins. This package is a function which takes two arguments: plugins, a list of nix derivations to include as plugins (loaded only when specified in rebar.config), and globalPlugins, which should always be loaded by rebar3. Example: beamPackages.rebar3WithPlugins { globalPlugins = [beamPackages.pc]; }.

When adding a new plugin it is important that the name attribute is the same as the atom used by rebar3 to refer to the plugin.

Erlang.mk

Erlang.mk works exactly as expected. There is a bootstrap process that needs to be run, which is supported by the buildErlangMk derivation.

Mix

For Elixir applications that use mix release, use the mixRelease builder to make a release. See examples for more details.

There is also a buildMix helper, whose behavior is closer to that of buildErlangMk and buildRebar3. The primary difference is that mixRelease makes a release, while buildMix only builds the package, which is more useful for libraries and other dependencies.

How to Install BEAM Packages

To use any of these builders in your environment, refer to them by their attribute path under beamPackages (or another BEAM package set), e.g. beamPackages.rebar3:

Example 381. Ephemeral shell
$ nix-shell -p beamPackages.rebar3

Example 382. Declarative shell
let
  pkgs = import <nixpkgs> {
    config = { };
    overlays = [ ];
  };
in
pkgs.mkShell { packages = [ pkgs.beamPackages.rebar3 ]; }

Packaging BEAM Applications

Erlang Applications

Rebar3 Packages

The builder beamPackages.buildRebar3 can be used to build a derivation that understands how to build a Rebar3 project.

Erlang.mk Packages

Erlang.mk functions similarly to Rebar3, except we use beamPackages.buildErlangMk instead of beamPackages.buildRebar3.

If a package needs to compile native code via Erlang.mk’s port compilation mechanism, add compilePorts = true; to the derivation.

Elixir Applications

Mix Packages

beamPackages.mixRelease is used to make a release in the mix sense. Dependencies will need to be fetched with beamPackages.fetchMixDeps and passed to it.

mixRelease - Elixir Phoenix example

There are 3 steps: frontend dependencies (javascript), backend dependencies (elixir), and the final derivation that puts both of those together.

mixRelease - Frontend dependencies (javascript)

For phoenix projects, inside of Nixpkgs you can either use fetchYarnDeps or buildNpmPackage. An example with buildNpmPackage can be found here, and an example with fetchYarnDeps can be found here.

mixRelease - backend dependencies (mix)

There are 2 ways to package backend dependencies: either per-dependency mix2nix or with a fixed-output-derivation (FOD).

When writing an elixir project targeting mixRelease, you can also consider using deps_nix with mixNixDeps. deps_nix supports git dependencies, but is intended to be added to the project’s mix.exs directly.

mix2nix

mix2nix is a cli tool available in Nixpkgs. It will generate a Nix expression from a mix.lock file. It is quite standard in the 2nix tool series.

Note that currently mix2nix can’t handle git dependencies inside the mix.lock file. If you have git dependencies, you can either add them manually (see example) or use the FOD method.

The advantage of using mix2nix is that nix will know your whole dependency graph. On a dependency update, this won’t trigger a full rebuild and download of all the dependencies, where FOD will do so.

Practical steps:

  • run mix2nix > mix_deps.nix in the upstream repo.

  • pass mixNixDeps = with pkgs; import ./mix_deps.nix { inherit lib beamPackages; }; as an argument to mixRelease.

If there are git dependencies.

  • You’ll need to fix the version artificially in mix.exs and regenerate the mix.lock with fixed version (on upstream). This will enable you to run mix2nix > mix_deps.nix.

  • From the mix_deps.nix file, remove the dependencies that had git versions and pass them as an override to the import function.

{
  mixNixDeps = import ./mix.nix {
    inherit beamPackages lib;
    overrides = (
      final: prev: {
        # mix2nix does not support git dependencies yet,
        # so we need to add them manually
        prometheus_ex = beamPackages.buildMix rec {
          name = "prometheus_ex";
          version = "3.0.5";

          # Change the argument src with the git src that you actually need
          src = fetchFromGitLab {
            domain = "git.pleroma.social";
            group = "pleroma";
            owner = "elixir-libraries";
            repo = "prometheus.ex";
            rev = "a4e9beb3c1c479d14b352fd9d6dd7b1f6d7deee5";
            hash = "sha256-U17LlN6aGUKUFnT4XyYXppRN+TvUBIBRHEUsfeIiGOw=";
          };
          # you can re-use the same beamDeps argument as generated
          beamDeps = with final; [ prometheus ];
        };
      }
    );
  };
}

You will need to run the build process once to fix the hash to correspond to your new git src.

FOD

A fixed output derivation will download mix dependencies from the internet. To ensure reproducibility, a hash will be supplied. Note that mix is relatively reproducible. An FOD generating a different hash on each run hasn’t been observed (as opposed to npm where the chances are relatively high). See akkoma for a usage example of FOD.

Practical steps

  • start with the following argument to mixRelease

{
  mixFodDeps = fetchMixDeps {
    pname = "mix-deps-${pname}";
    inherit src version;
    hash = lib.fakeHash;
  };
}

The first build will complain about the hash value, you can replace with the suggested value after that.

Note that if after you’ve replaced the value, nix suggests another hash, then mix is not fetching the dependencies reproducibly. An FOD will not work in that case and you will have to use mix2nix.

mixRelease - example

Here is how your default.nix file would look for a Phoenix project.

{
  # beam27Packages or beam29Packages is available if you need a particular version
  beamPackages,
}:
let
  pname = "your_project";
  version = "0.0.1";

  src = builtins.fetchgit {
    url = "ssh://git@github.com/your_id/your_repo";
    rev = "replace_with_your_commit";
  };

  # if using mix2nix you can use the mixNixDeps attribute
  mixFodDeps = beamPackages.fetchMixDeps {
    pname = "mix-deps-${pname}";
    inherit src version;
    # nix will complain and tell you the right value to replace this with
    hash = lib.fakeHash;
    mixEnv = ""; # default is "prod", when empty includes all dependencies, such as "dev", "test".
    # if you have build time environment variables add them here
    MY_ENV_VAR = "my_value";
  };
in
beamPackages.mixRelease {
  inherit
    src
    pname
    version
    mixFodDeps
    ;
  # if you have build time environment variables add them here
  MY_ENV_VAR = "my_value";

  postBuild = ''
    # for external task you need a workaround for the no deps check flag
    # https://github.com/phoenixframework/phoenix/issues/2690
    mix do deps.loadpaths --no-deps-check, phx.digest
    mix phx.digest --no-deps-check
  '';
}

Setup will require the following steps:

  • Move your secrets to runtime environment variables. For more information refer to the runtime.exs docs. On a fresh Phoenix build that would mean that both DATABASE_URL and SECRET_KEY need to be moved to runtime.exs.

  • Generate a Nix expression for your frontend dependencies using fetchNpmDeps/buildNpmPackage or fetchYarnDeps, depending on whether the project uses npm or yarn

  • commit and push those changes

  • you can now nix-build .

  • To run the release, set the RELEASE_TMP environment variable to a directory that your program has write access to. It will be used to store the BEAM settings.

Example of creating a service for an Elixir - Phoenix project

In order to create a service with your release, you could add a service.nix in your project with the following

{
  config,
  pkgs,
  lib,
  ...
}:

let
  release = pkgs.callPackage ./default.nix { };
  release_name = "app";
  working_directory = "/home/app";
in
{
  systemd.services.${release_name} = {
    wantedBy = [ "multi-user.target" ];
    after = [
      "network.target"
      "postgresql.target"
    ];
    # note that if you are connecting to a postgres instance on a different host
    # postgresql.target should not be included in the requires.
    requires = [
      "network-online.target"
      "postgresql.target"
    ];
    description = "my app";
    environment = {
      # RELEASE_TMP is used to write the state of the
      # VM configuration when the system is running
      # it needs to be a writable directory
      RELEASE_TMP = working_directory;
      # can be generated in an elixir console with
      # Base.encode32(:crypto.strong_rand_bytes(32))
      RELEASE_COOKIE = "my_cookie";
      MY_VAR = "my_var";
    };
    serviceConfig = {
      Type = "exec";
      DynamicUser = true;
      WorkingDirectory = working_directory;
      # Implied by DynamicUser, but just to emphasize due to RELEASE_TMP
      PrivateTmp = true;
      ExecStart = ''
        ${release}/bin/${release_name} start
      '';
      ExecStop = ''
        ${release}/bin/${release_name} stop
      '';
      ExecReload = ''
        ${release}/bin/${release_name} restart
      '';
      Restart = "on-failure";
      RestartSec = 5;
    };
    unitConfig = {
      StartLimitBurst = 3;
      StartLimitInterval = 10;
    };
    # disksup requires bash
    path = [ pkgs.bash ];
  };

  # in case you have migration scripts or you want to use a remote shell
  environment.systemPackages = [ release ];
}

How to Develop

Creating a Shell

Usually, we need to create a shell.nix file and do our development inside the environment specified therein. Just install your version of Erlang and any other interpreters, and then use your normal build tools. As an example, with Elixir:

{
  pkgs ? import <nixpkgs> { },
}:

with pkgs;
let
  # pin OTP via beam27Packages/beam28Packages/... and Elixir via .extend
  beamPackages = beam27Packages.extend (self: super: { elixir = self.elixir_1_18; });
in
mkShell { buildInputs = [ beamPackages.elixir ]; }

Using an overlay

If you need to use an overlay to change some attributes of a derivation, e.g. if you need a bugfix from a version that is not yet available in Nixpkgs, you can override attributes such as version (and the corresponding hash) and then use this overlay in your development environment:

shell.nix
let
  elixir_1_18_1_overlay = (
    self: super: {
      elixir_1_18 = super.elixir_1_18.override {
        version = "1.18.1";
        hash = "sha256-AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=";
      };
    }
  );
  pkgs = import <nixpkgs> { overlays = [ elixir_1_18_1_overlay ]; };
in
with pkgs;
mkShell { buildInputs = [ elixir_1_18 ]; }
Elixir - Phoenix project

Here is an example shell.nix.

with import <nixpkgs> { };

let
  # pin OTP via beam27Packages/beam28Packages/... and Elixir via .extend
  beamPackages = beam27Packages.extend (self: super: { elixir = self.elixir_1_18; });

  # define packages to install
  basePackages = [
    git
    beamPackages.elixir
    nodejs
    postgresql_14
    # formatting js file
    prettier
  ];

  inputs = basePackages ++ lib.optionals stdenv.hostPlatform.isLinux [ inotify-tools ];

  # define shell startup command
  hooks = ''
    # this allows mix to work on the local directory
    mkdir -p .nix-mix .nix-hex
    export MIX_HOME=$PWD/.nix-mix
    export HEX_HOME=$PWD/.nix-mix
    # make hex from Nixpkgs available
    # `mix local.hex` will install hex into MIX_HOME and should take precedence
    export MIX_PATH="${beamPackages.hex}/lib/erlang/lib/hex/ebin"
    export PATH=$MIX_HOME/bin:$HEX_HOME/bin:$PATH
    export LANG=C.UTF-8
    # keep your shell history in iex
    export ERL_AFLAGS="-kernel shell_history enabled"

    # postgres related
    # keep all your db data in a folder inside the project
    export PGDATA="$PWD/db"

    # phoenix related env vars
    export POOL_SIZE=15
    export DB_URL="postgresql://postgres:postgres@localhost:5432/db"
    export PORT=4000
    export MIX_ENV=dev
    # add your project env vars here, word readable in the nix store.
    export ENV_VAR="your_env_var"
  '';

in
mkShell {
  buildInputs = inputs;
  shellHook = hooks;
}

Initializing the project will require the following steps:

  • create the db directory initdb ./db (inside your mix project folder)

  • create the postgres user createuser postgres -ds

  • create the db createdb db

  • start the postgres instance pg_ctl -l "$PGDATA/server.log" start

  • add the /db folder to your .gitignore

  • you can start your Phoenix server and get a shell with iex -S mix phx.server

CHICKEN

CHICKEN is a R⁵RS-compliant Scheme compiler. It includes an interactive mode and a custom package format, “eggs”.

Using Eggs

Eggs described in Nixpkgs are available inside the chickenPackages.chickenEggs attrset. Including an egg as a build input is done in the typical Nix fashion. For example, to include support for SRFI 189 in a derivation, one might write:

{
  buildInputs = [
    chicken
    chickenPackages.chickenEggs.srfi-189
  ];
}

Both chicken and its eggs have a setup hook which configures the environment variables CHICKEN_INCLUDE_PATH and CHICKEN_REPOSITORY_PATH.

Updating Eggs

Nixpkgs only knows about a subset of all published eggs. It uses egg2nix to generate a package set from a list of eggs to include.

The package set is regenerated by running the following shell commands:

$ nix-shell -p chickenPackages.egg2nix
$ cd pkgs/development/compilers/chicken/5/
$ egg2nix eggs.scm > eggs.nix

Adding Eggs

When we run egg2nix, we obtain one collection of eggs with mutually-compatible versions. This means that when we add new eggs, we may need to update existing eggs. To keep those separate, follow the procedure for updating eggs before including more eggs.

To include more eggs, edit pkgs/development/compilers/chicken/5/eggs.scm. The first section of this file lists eggs which are required by egg2nix itself; all other eggs go into the second section. After editing, follow the procedure for updating eggs.

Override Scope

The chicken package and its eggs, respectively, reside in a scope. This means, the scope can be overridden to affect other packages in it.

This example shows how to use a local copy of srfi-180 and have it affect all the other eggs:

let
  myChickenPackages = pkgs.chickenPackages.overrideScope (
    self: super: {
      # The chicken package itself can be overridden to affect the whole ecosystem.
      # chicken = super.chicken.overrideAttrs {
      #   src = ...
      # };

      chickenEggs = super.chickenEggs.overrideScope (
        eggself: eggsuper: {
          srfi-180 = eggsuper.srfi-180.overrideAttrs {
            # path to a local copy of srfi-180
            src = <...>;
          };
        }
      );
    }
  );
  # Here, `myChickenPackages.chickenEggs.json-rpc`, which depends on `srfi-180` will use
  # the local copy of `srfi-180`.
in
<...>

Rocq and rocq packages

Note that “The Rocq Prover” (Rocq for short) is the new name of the proof assistant formerly known as Coq. The coq and coqPackages derivations currently remain for both older versions of Coq, but also some versions of Rocq during the renaming transition. In the latter case, the coq derivation encompasses the compatibility binaries (coqtop, coqc, etc.) in addition to the rocq binary. The packages only in coqPackages are the ones which currently still depend on these compatibility binaries.

Rocq derivation: rocq-core

The Rocq derivation is overridable through the rocq-core.override overrides, where overrides is an attribute set which contains the arguments to override. We recommend overriding either of the following:

  • version (optional, defaults to the latest version of Rocq selected for nixpkgs, see pkgs/top-level/rocq-packages to witness this choice), which follows the conventions explained in the rocqPackages section below,

  • customOCamlPackages (optional, defaults to null, which lets Rocq choose a version automatically), which can be set to any of the ocaml packages attribute of ocaml-ng (such as ocaml-ng.ocamlPackages_4_14 which is the default for Rocq 9.1 for example).

  • rocq-version (optional, defaults to the short version e.g. “9.1”), is a version number of the form “x.y” that indicates which Rocq’s version build behavior to mimic when using a source which is not a release. E.g. rocq-core.override { version = "40be8435e132aab2231a79091f011ebc3e64a753"; rocq-version = "9.1"; }.

Creating custom Coq environments with coq.withPackages

The coq.withPackages function provides a convenient way to create a Coq environment that includes additional Coq packages. This is similar to how python.withPackages works for Python environments.

The function takes a function that receives the Coq package set and returns a list of packages. It returns a wrapped Coq environment where all Coq binaries (coqtop, coqc, coqdep, coqchk, coqide, etc.) are configured with the appropriate environment variables to find the packages.

Usage

Here is an example of creating a Coq environment with specific packages.

coq.withPackages (
  ps: with ps; [
    mathcomp
    bignums
  ]
)

If you install the vsrocq-language-server or rocq-lsp server, make sure to list them as part of the above coq.withPackages expression instead of installing them separately if you want them to find your Coq/Rocq packages.

Rocq packages attribute sets: rocqPackages

The recommended way of defining a derivation for a Rocq library, is to use the rocqPackages.mkRocqDerivation function, which is essentially a specialization of mkDerivation taking into account most of the specifics of Rocq libraries. The following attributes are supported:

  • pname (required) is the name of the package,

  • version (optional, defaults to null), is the version to fetch and build, this attribute is interpreted in several ways depending on its type and pattern:

    • if it is a known released version string, i.e. from the release attribute below, the according release is picked, and the version attribute of the resulting derivation is set to this release string,

    • if it is a majorMinor "x.y" prefix of a known released version (as defined above), then the latest "x.y.z" known released version is selected (for the ordering given by versionAtLeast),

    • if it is a path or a string representing an absolute path (i.e. starting with "/"), the provided path is selected as a source, and the version attribute of the resulting derivation is set to "dev",

    • if it is a string of the form owner:branch then it tries to download the branch of owner owner for a project of the same name using the same vcs, and the version attribute of the resulting derivation is set to "dev", additionally if the owner is not provided (i.e. if the owner: prefix is missing), it defaults to the original owner of the package (see below),

    • if it is a string of the form "#N", and the domain is github, then it tries to download the current head of the pull request #N from github,

  • defaultVersion (optional). Rocq libraries may be compatible with some specific versions of Rocq only. The defaultVersion attribute is used when no version is provided (or if version = null) to select the version of the library to use by default, depending on the context. This selection will mainly depend on a rocq-core version number but also possibly on other packages versions (e.g. mathcomp). If its value ends up to be null, the package is marked for removal in end-user rocqPackages attribute set.

  • release (optional, defaults to {}), lists all the known releases of the library and for each of them provides an attribute set with at least a hash attribute (you may put the empty string "" in order to automatically insert a fake hash, this will trigger an error which will allow you to find the correct hash), each attribute set of the list of releases also takes optional overloading arguments for the fetcher as below (i.e.domain, owner, repo, rev, artifact assuming the default fetcher is used) and optional overrides for the result of the fetcher (i.e. version and src).

  • fetcher (optional, defaults to a generic fetching mechanism supporting github or gitlab based infrastructures), is a function that takes at least an owner, a repo, a rev, and a hash and returns an attribute set with a version and src.

  • repo (optional, defaults to the value of pname),

  • owner (optional, defaults to "rocq-community").

  • domain (optional, defaults to "github.com"), domains including the strings "github" or "gitlab" in their names are automatically supported, otherwise, one must change the fetcher argument to support them (cf pkgs/development/rocq-modules/bignums/default.nix for an example),

  • releaseRev (optional, defaults to (v: v)), provides a default mapping from release names to revision hashes/branch names/tags,

  • releaseArtifact (optional, defaults to (v: null)), provides a default mapping from release names to artifact names (only works for github artifact for now),

  • displayVersion (optional), provides a way to alter the computation of name from pname, by explaining how to display version numbers,

  • namePrefix (optional, defaults to [ "rocq-core" ]), provides a way to alter the computation of name from pname, by explaining which dependencies must occur in name,

  • nativeBuildInputs (optional), is a list of executables that are required to build the current derivation, in addition to the default ones (namely which, dune and ocaml depending on whether useDune, useDuneifVersion and mlPlugin are set).

  • extraNativeBuildInputs (optional, deprecated), an additional list of derivation to add to nativeBuildInputs,

  • overrideNativeBuildInputs (optional) replaces the default list of derivation to which nativeBuildInputs and extraNativeBuildInputs adds extra elements,

  • buildInputs (optional), is a list of libraries and dependencies that are required to build and run the current derivation, in addition to the default one [ rocq-core ],

  • extraBuildInputs (optional, deprecated), an additional list of derivation to add to buildInputs,

  • overrideBuildInputs (optional) replaces the default list of derivation to which buildInputs and extraBuildInputs adds extras elements,

  • propagatedBuildInputs (optional) is passed as is to mkDerivation, we recommend to use this for Rocq libraries and Rocq plugin dependencies, as this makes sure the paths of the compiled libraries and plugins will always be added to the build environments of subsequent derivation, which is necessary for Rocq packages to work correctly,

  • mlPlugin (optional, defaults to false). Some extensions (plugins) might require OCaml and sometimes other OCaml packages. Standard dependencies can be added by setting the current option to true. For a finer grain control, the rocq-core.ocamlPackages attribute can be used in nativeBuildInputs, buildInputs, and propagatedBuildInputs to depend on the same package set Rocq was built against.

  • useDuneifVersion (optional, default to (x: false) uses Dune to build the package if the provided predicate evaluates to true on the version, e.g. useDuneifVersion = versions.isGe "1.1" will use dune if the version of the package is greater or equal to "1.1",

  • useDune (optional, defaults to false) uses Dune to build the package if set to true, the presence of this attribute overrides the behavior of the previous one.

  • opam-name (optional, defaults to concatenating with a dash separator the components of namePrefix and pname), name of the Dune package to build.

  • enableParallelBuilding (optional, defaults to true), since it is activated by default, we provide a way to disable it.

  • extraInstallFlags (optional), allows to extend installFlags which initializes the variables COQLIBINSTALL and COQPLUGININSTALL so as to install in the proper subdirectory. Indeed Rocq libraries should be installed in $(out)/lib/coq/${rocq-core.rocq-version}/user-contrib/. Such directories are automatically added to the $ROCQPATH environment variable by the hook defined in the Rocq derivation.

  • setROCQBIN (optional, defaults to true), by default, the environment variable $ROCQBIN is set to the current Rocq’s binary, but one can disable this behavior by setting it to false,

  • useMelquiondRemake (optional, default to null) is an attribute set, which, if given, overloads the preConfigurePhases, configureFlags, buildPhase, and installPhase attributes of the derivation for a specific use in libraries using remake as set up by Guillaume Melquiond for flocq, gappalib, interval, and coquelicot (see the corresponding derivation for concrete examples of use of this option). For backward compatibility, the attribute useMelquiondRemake.logpath must be set to the logical root of the library (otherwise, one can pass useMelquiondRemake = {} to activate this without backward compatibility).

  • dropAttrs, keepAttrs, dropDerivationAttrs are all optional and allow to tune which attribute is added or removed from the final call to mkDerivation.

It also takes other standard mkDerivation attributes, they are added as such, except for meta which extends an automatically computed meta (where the platform is the same as rocq-core and the homepage is automatically computed).

Here is a simple package example. It is a pure Rocq library, thus it depends on Rocq. It builds on the Mathematical Components library, thus it also takes some mathcomp derivations as extraBuildInputs.

{
  lib,
  mkRocqDerivation,
  version ? null,
  rocq-core,
  mathcomp,
  mathcomp-finmap,
  mathcomp-bigenough,
}:

mkRocqDerivation {
  # namePrefix leads to e.g. `name = rocq-core9.1-mathcomp2.5.0-multinomials-2.4.0`
  namePrefix = [
    "rocq-core"
    "mathcomp"
  ];
  pname = "multinomials";
  owner = "math-comp";
  inherit version;
  defaultVersion =
    let
      case = rocq: mc: out: {
        cases = [
          rocq-core
          mc
        ];
        inherit out;
      };
    in
    with lib.versions;
    lib.switch
      [ rocq-core.rocq-version mathcomp.version ]
      [
        (case (range "8.18" "9.1") (range "2.1.0" "2.5.0") "2.4.0")
        (case (range "8.17" "9.0") (range "2.1.0" "2.3.0") "2.3.0")
      ]
      null;
  release = {
    "2.4.0".sha256 = "sha256-7zfIddRH+Sl4nhEPtS/lMZwRUZI45AVFpcC/UC8Z0Yo=";
    "2.3.0".sha256 = "sha256-usIcxHOAuN+f/j3WjVbPrjz8Hl9ac8R6kYeAKi3CEts=";
  };

  propagatedBuildInputs = [
    mathcomp.boot
    mathcomp.algebra
    mathcomp-finmap
    mathcomp.fingroup
    mathcomp-bigenough
  ];

  meta = {
    description = "Coq/SSReflect Library for Monoidal Rings and Multinomials";
    license = lib.licenses.cecill-c;
  };
}

Three ways of overriding Rocq packages

There are three distinct ways of changing a Rocq package by overriding one of its values: .override, overrideRocqDerivation, and .overrideAttrs. This section explains what sort of values can be overridden with each of these methods.

.override

.override lets you change arguments to a Rocq derivation. In the case of the multinomials package above, .override would let you override arguments like mkRocqDerivation, version, rocq-core, mathcomp, mathcom-finmap, etc.

For example, assuming you have a special mathcomp dependency you want to use, here is how you could override the mathcomp dependency:

multinomials.override { mathcomp = my-special-mathcomp; }

In Nixpkgs, all Rocq derivations take a version argument. This can be overridden in order to easily use a different version:

rocqPackages.multinomials.override { version = "1.5.1"; }

Refer to the section called “Rocq packages attribute sets: rocqPackages for all the different formats that you can potentially pass to version, as well as the restrictions.

overrideRocqDerivation

The overrideRocqDerivation function lets you easily change arguments to mkRocqDerivation. These arguments are described in the section called “Rocq packages attribute sets: rocqPackages.

For example, here is how you could locally add a new release of the multinomials library, and set the defaultVersion to use this release:

rocqPackages.lib.overrideRocqDerivation {
  defaultVersion = "2.0";
  release."2.0".hash = "sha256-czoP11rtrIM7+OLdMisv2EF7n/IbGuwFxHiPtg3qCNM=";
} rocqPackages.multinomials

.overrideAttrs

.overrideAttrs lets you override arguments to the underlying stdenv.mkDerivation call. Internally, mkRocqDerivation uses stdenv.mkDerivation to create derivations for Rocq libraries. You can override arguments to stdenv.mkDerivation with .overrideAttrs.

For instance, here is how you could add some code to be performed in the derivation after installation is complete:

rocqPackages.multinomials.overrideAttrs (oldAttrs: {
  postInstall = oldAttrs.postInstall or "" + ''
    echo "you can do anything you want here"
  '';
})

COSMIC

Packaging COSMIC applications

COSMIC (Computer Operating System Main Interface Components) is a desktop environment developed by System76, primarily for the Pop!_OS Linux distribution. Applications in the COSMIC ecosystem are written in Rust and use libcosmic, which builds on the Iced GUI framework. This section explains how to properly package and integrate COSMIC applications within Nix.

libcosmicAppHook

The libcosmicAppHook is a setup hook that helps with this by automatically configuring and wrapping applications based on libcosmic. It handles many common requirements like:

  • Setting up proper linking for libraries that may be dlopen’d by libcosmic/iced apps

  • Configuring XDG paths for settings schemas, icons, and other resources

  • Managing Vergen environment variables for build-time information

  • Setting up Rust linker flags for specific libraries

To use the hook, simply add it to your package’s nativeBuildInputs:

{
  lib,
  rustPlatform,
  libcosmicAppHook,
}:
rustPlatform.buildRustPackage {
  # ...
  nativeBuildInputs = [ libcosmicAppHook ];
  # ...
}

Settings fallback

COSMIC applications use libcosmic’s UI components, which may need access to theme settings. The cosmic-settings package provides default theme settings as a fallback in its share directory. By default, libcosmicAppHook includes this fallback path in XDG_DATA_DIRS, ensuring that COSMIC applications will have access to theme settings even if they aren’t available elsewhere in the system.

This fallback behavior can be disabled by setting includeSettings = false when including the hook:

{
  lib,
  rustPlatform,
  libcosmicAppHook,
}:
let
  # Get build-time version of libcosmicAppHook
  libcosmicAppHook' = (libcosmicAppHook.__spliced.buildHost or libcosmicAppHook).override {
    includeSettings = false;
  };
in
rustPlatform.buildRustPackage {
  # ...
  nativeBuildInputs = [ libcosmicAppHook' ];
  # ...
}

Note that cosmic-settings is a separate application and not a part of the libcosmic settings system itself. It’s included by default in libcosmicAppHook only to provide these fallback theme settings.

Icons

COSMIC applications can use icons from the COSMIC icon theme. While COSMIC applications can build and run without these icons, they would be missing visual elements. The libcosmicAppHook automatically includes cosmic-icons in the wrapped application’s XDG_DATA_DIRS as a fallback, ensuring that the application has access to its required icons even if the system doesn’t have the COSMIC icon theme installed globally.

Unlike the cosmic-settings fallback, the cosmic-icons fallback cannot be removed or disabled, as it is essential for COSMIC applications to have access to these icons for proper visual rendering.

Runtime Libraries

COSMIC applications built on libcosmic and Iced require several runtime libraries that are dlopen’d rather than linked directly. The libcosmicAppHook ensures that these libraries are correctly linked by setting appropriate Rust linker flags. The libraries handled include:

  • Graphics libraries (EGL, Vulkan)

  • Input libraries (xkbcommon)

  • Display server protocols (Wayland, X11)

This ensures that the applications will work correctly at runtime, even though they use dynamic loading for these dependencies.

Adding custom wrapper arguments

You can pass additional arguments to the wrapper using libcosmicAppWrapperArgs in the preFixup hook:

{
  lib,
  rustPlatform,
  libcosmicAppHook,
}:
rustPlatform.buildRustPackage {
  # ...
  preFixup = ''
    libcosmicAppWrapperArgs+=(--set-default ENVIRONMENT_VARIABLE VALUE)
  '';
  # ...
}

Frequently encountered issues

Setting up Vergen environment variables

Many COSMIC applications use the Vergen Rust crate for build-time information. The libcosmicAppHook automatically sets up the VERGEN_GIT_COMMIT_DATE environment variable based on SOURCE_DATE_EPOCH to ensure reproducible builds.

However, some applications may explicitly require additional Vergen environment variables. Without these properly set, you may encounter build failures with errors like:

>   cargo:rerun-if-env-changed=VERGEN_GIT_COMMIT_DATE
>   cargo:rerun-if-env-changed=VERGEN_GIT_SHA
>
>   --- stderr
>   Error: no suitable 'git' command found!
> warning: build failed, waiting for other jobs to finish...

While libcosmicAppHook handles VERGEN_GIT_COMMIT_DATE, you may need to explicitly set other variables. For applications that require these variables, you should set them directly in the package definition:

{
  lib,
  rustPlatform,
  libcosmicAppHook,
}:
rustPlatform.buildRustPackage {
  # ...
  env = {
    VERGEN_GIT_COMMIT_DATE = "2025-01-01";
    VERGEN_GIT_SHA = "0000000000000000000000000000000000000000"; # SHA-1 hash of the commit
  };
  # ...
}

Not all COSMIC applications require these variables, but for those that do, setting them explicitly will prevent build failures.

Crystal

Building a Crystal package

This section uses Mint as an example for how to build a Crystal package.

If the Crystal project has any dependencies, the first step is to get a shards.nix file encoding those. Get a copy of the project and go to its root directory such that its shard.lock file is in the current directory. Executable projects should usually commit the shard.lock file, but sometimes that’s not the case, which means you need to generate it yourself. With an existing shard.lock file, crystal2nix can be run.

$ git clone https://github.com/mint-lang/mint
$ cd mint
$ git checkout 0.5.0
$ if [ ! -f shard.lock ]; then nix-shell -p shards --run "shards lock"; fi
$ nix-shell -p crystal2nix --run crystal2nix

This should have generated a shards.nix file.

Next create a Nix file for your derivation and use pkgs.crystal.buildCrystalPackage as follows:

with import <nixpkgs> { };
crystal.buildCrystalPackage rec {
  pname = "mint";
  version = "0.5.0";

  src = fetchFromGitHub {
    owner = "mint-lang";
    repo = "mint";
    tag = version;
    hash = "sha256-dFN9l5fgrM/TtOPqlQvUYgixE4KPr629aBmkwdDoq28=";
  };

  # Insert the path to your shards.nix file here
  shardsFile = ./shards.nix;

  # ...
}

This won’t build anything yet, because we haven’t told it what files build. We can specify a mapping from binary names to source files with the crystalBinaries attribute. The project’s compilation instructions should show this. For Mint, the binary is called “mint”, which is compiled from the source file src/mint.cr, so we’ll specify this as follows:

{
  crystalBinaries.mint.src = "src/mint.cr";

  # ...
}

Additionally you can override the default crystal build options (which are currently --release --progress --no-debug --verbose) with

{
  crystalBinaries.mint.options = [
    "--release"
    "--verbose"
  ];
}

Depending on the project, you might need additional steps to get it to compile successfully. In Mint’s case, we need to link against openssl, so in the end the Nix file looks as follows:

with import <nixpkgs> { };
crystal.buildCrystalPackage rec {
  version = "0.5.0";
  pname = "mint";
  src = fetchFromGitHub {
    owner = "mint-lang";
    repo = "mint";
    tag = version;
    hash = "sha256-dFN9l5fgrM/TtOPqlQvUYgixE4KPr629aBmkwdDoq28=";
  };

  shardsFile = ./shards.nix;
  crystalBinaries.mint.src = "src/mint.cr";

  buildInputs = [ openssl ];
}

CUDA

Compute Unified Device Architecture (CUDA) is a parallel computing platform and application programming interface (API) model created by NVIDIA. It’s commonly used to accelerate computationally intensive problems and has been widely adopted for high-performance computing (HPC) and machine learning (ML) applications.

User Guide

Packages provided by NVIDIA which require CUDA are typically stored in CUDA package sets.

Nixpkgs provides a number of CUDA package sets, each based on a different CUDA release. Top-level attributes that provide access to CUDA package sets follow these naming conventions:

  • cudaPackages_x_y: A major-minor-versioned package set for a specific CUDA release, where x and y are the major and minor versions of the CUDA release.

  • cudaPackages_x: A major-versioned alias to the major-minor-versioned CUDA package set with the latest widely supported major CUDA release.

  • cudaPackages: An unversioned alias to the major-versioned alias for the latest widely supported CUDA release. The package set referenced by this alias is also referred to as the “default” CUDA package set.

It is recommended to use the unversioned cudaPackages attribute. While versioned package sets are available (e.g., cudaPackages_12_8), they are periodically removed.

Here are two examples to illustrate the naming conventions:

  • If cudaPackages_12_9 is the latest release in the 12.x series, but core libraries like OpenCV or ONNX Runtime fail to build with it, cudaPackages_12 may alias cudaPackages_12_8 instead of cudaPackages_12_9.

  • If cudaPackages_13_1 is the latest release, but core libraries like PyTorch or Torch Vision fail to build with it, cudaPackages may alias cudaPackages_12 instead of cudaPackages_13.

All CUDA package sets include common CUDA packages like libcublas, cudnn, tensorrt, and nccl.

Configuring Nixpkgs for CUDA

CUDA support is not enabled by default in Nixpkgs. To enable CUDA support, make sure Nixpkgs is imported with a configuration similar to the following:

{ pkgs }:
{
  allowUnfreePredicate = pkgs._cuda.lib.allowUnfreeCudaPredicate;
  cudaCapabilities = [ <target-architectures> ];
  cudaForwardCompat = true;
  cudaSupport = true;
}

The majority of CUDA packages are unfree, so either allowUnfreePredicate or allowUnfree should be set.

The cudaSupport configuration option is used by packages to conditionally enable CUDA-specific functionality. This configuration option is commonly used by packages which can be built with or without CUDA support.

The cudaCapabilities configuration option specifies a list of CUDA capabilities. Packages may use this option to control device code generation to take advantage of architecture-specific functionality, speed up compile times by producing less device code, or slim package closures. For example, you can build for Ada Lovelace GPUs with cudaCapabilities = [ "8.9" ];. If cudaCapabilities is not provided, the default value is calculated per-package set, derived from a list of GPUs supported by that CUDA version. Please consult supported GPUs for specific cards. Library maintainers should consult NVCC Docs and its release notes.

Caution

Certain CUDA capabilities are not targeted by default, including capabilities belonging to the Jetson family of devices (e.g. 8.7, which corresponds to the Jetson Orin) or non-baseline feature-sets (e.g. 9.0a, which corresponds to the Hopper exclusive feature set). If you need to target these capabilities, you must explicitly set cudaCapabilities to include them.

The cudaForwardCompat boolean configuration option determines whether PTX support for future hardware is enabled.

Modifying CUDA package sets

CUDA package sets are defined in pkgs/top-level/cuda-packages.nix. A CUDA package set is created by callPackage-ing pkgs/development/cuda-modules/default.nix with an attribute set manifests, containing NVIDIA manifests for each redistributable. The manifests for supported redistributables are available through _cuda.manifests and live in pkgs/development/cuda-modules/_cuda/manifests.

The majority of the CUDA package set tooling is available through the top-level attribute set _cuda, a fixed-point defined outside the CUDA package sets. As a fixed-point, _cuda should be modified through its extend attribute.

Caution

As indicated by the underscore prefix, _cuda is an implementation detail and no guarantees are provided with respect to its stability or API. The _cuda attribute set is exposed only to ease creation or modification of CUDA package sets by expert, out-of-tree users.

Out-of-tree modifications of packages should use overrideAttrs to make any necessary modifications to the package expression.

Note

The _cuda attribute set previously exposed fixups, an attribute set mapping from package name (pname) to a callPackage-compatible expression which provided to overrideAttrs on the result of a generic redistributable builder. This functionality has been removed in favor of including full package expressions for each redistributable package to ensure consistent attribute set membership across supported CUDA releases, platforms, and configurations.

Extending CUDA package sets

CUDA package sets are scopes and provide the usual overrideScope attribute for overriding package attributes (see the note about _cuda in Configuring CUDA package sets).

Inspired by pythonPackagesExtensions, the _cuda.extensions attribute is a list of extensions applied to every version of the CUDA package set, allowing modification of all versions of the CUDA package set without needing to know their names or explicitly enumerate and modify them. As an example, disabling cuda_compat across all CUDA package sets can be accomplished with this overlay:

final: prev: {
  _cuda = prev._cuda.extend (
    _: prevAttrs: {
      extensions = prevAttrs.extensions ++ [ (_: _: { cuda_compat = null; }) ];
    }
  );
}

Redistributable packages are constructed by the buildRedist helper; see pkgs/development/cuda-modules/buildRedist/default.nix for the implementation.

Using cudaPackages

Caution

A non-trivial amount of CUDA package discoverability and usability relies on the various setup hooks used by a CUDA package set. As a result, users will likely encounter issues trying to perform builds within a devShell without manually invoking phases.

To use one or more CUDA packages in an expression, give the expression a cudaPackages parameter, and in case CUDA support is optional, add a config and cudaSupport parameter:

{
  config,
  cudaSupport ? config.cudaSupport,
  cudaPackages,
}:
<package-expression>

In your package’s derivation arguments, it is strongly recommended that the following are set:

{
  __structuredAttrs = true;
  strictDeps = true;
}

These settings ensure that the CUDA setup hooks function as intended.

When using callPackage, you can choose to pass in a different variant, e.g. when a package requires a specific version of CUDA:

{ mypkg = callPackage { cudaPackages = cudaPackages_12_6; }; }

Caution

Overriding the CUDA package set for a package may cause inconsistencies, because the override does not affect its direct or transitive dependencies. As a result, it is easy to end up with a package that use a different CUDA package set than its dependencies. If possible, it is recommended that you change the default CUDA package set globally, to ensure a consistent environment.

Nixpkgs CUDA variants

Nixpkgs CUDA variants are provided primarily for the convenience of selecting CUDA-enabled packages by attribute path. As an example, the pkgsForCudaArch collection of CUDA Nixpkgs variants allows you to access an instantiation of OpenCV with CUDA support for an Ada Lovelace GPU with the attribute path pkgsForCudaArch.sm_89.opencv, without needing to modify the config provided when importing Nixpkgs.

Caution

Nixpkgs variants are not free: they require re-evaluating Nixpkgs. Where possible, import Nixpkgs once, with the desired configuration.

Using cudaPackages.pkgs

Each CUDA package set has a pkgs attribute, which is a variant of Nixpkgs in which the enclosing CUDA package set becomes the default. This was done primarily to avoid package set leakage, wherein a member of a non-default CUDA package set has a (potentially transitive) dependency on a member of the default CUDA package set.

Note

Package set leakage is a common problem in Nixpkgs and is not limited to CUDA package sets.

As an added benefit of pkgs being configured this way, building a package with a non-default version of CUDA is as simple as accessing an attribute. As an example, cudaPackages_12_8.pkgs.opencv provides OpenCV built against CUDA 12.8.

Using pkgsCuda

The pkgsCuda attribute set is a variant of Nixpkgs configured with cudaSupport = true; and rocmSupport = false. It is a convenient way to access a variant of Nixpkgs configured with the default set of CUDA capabilities.

Using pkgsForCudaArch

The pkgsForCudaArch attribute set maps CUDA architectures (e.g., sm_89 for Ada Lovelace or sm_90a for architecture-specific Hopper) to Nixpkgs variants configured to support exactly that architecture. As an example, pkgsForCudaArch.sm_89 is a Nixpkgs variant extending pkgs and setting the following values in config:

{
  cudaSupport = true;
  cudaCapabilities = [ "8.9" ];
  cudaForwardCompat = false;
}

Note

In pkgsForCudaArch, the cudaForwardCompat option is set to false because exactly one CUDA architecture is supported by the corresponding Nixpkgs variant. Furthermore, some architectures, including architecture-specific feature sets like sm_90a, cannot be built with forward compatibility.

Caution

Not every version of CUDA supports every architecture!

To illustrate: support for Blackwell (e.g., sm_100) was added in CUDA 12.8. Assume our Nixpkgs’ default CUDA package set is to CUDA 12.6. Then the Nixpkgs variant available through pkgsForCudaArch.sm_100 is useless, since packages like pkgsForCudaArch.sm_100.opencv and pkgsForCudaArch.sm_100.python3Packages.torch will try to generate code for sm_100, an architecture unknown to CUDA 12.6. In that case, you should use pkgsForCudaArch.sm_100.cudaPackages_12_8.pkgs instead (see Using cudaPackages.pkgs for more details).

The pkgsForCudaArch attribute set makes it possible to access packages built for a specific architecture without needing to manually call pkgs.extend and supply a new config. As an example, pkgsForCudaArch.sm_89.python3Packages.torch provides PyTorch built for Ada Lovelace GPUs.

Running Docker or Podman containers with CUDA support

It is possible to run Docker or Podman containers with CUDA support. The recommended mechanism to perform this task is to use the NVIDIA Container Toolkit.

The NVIDIA Container Toolkit can be enabled in NixOS like follows:

{ hardware.nvidia-container-toolkit.enable = true; }

This will automatically enable a service that generates a CDI specification (located at /var/run/cdi/nvidia-container-toolkit.json) based on the auto-detected hardware of your machine. You can check this service by running:

$ systemctl status nvidia-container-toolkit-cdi-generator.service

Note

Depending on what settings you had already enabled in your system, you might need to restart your machine in order for the NVIDIA Container Toolkit to generate a valid CDI specification for your machine.

Once that a valid CDI specification has been generated for your machine on boot time, both Podman and Docker (> 25) will use this spec if you provide them with the --device flag:

$ podman run --rm -it --device=nvidia.com/gpu=all ubuntu:latest nvidia-smi -L
GPU 0: NVIDIA GeForce RTX 4090 (UUID: <REDACTED>)
GPU 1: NVIDIA GeForce RTX 2080 SUPER (UUID: <REDACTED>)
$ docker run --rm -it --device=nvidia.com/gpu=all ubuntu:latest nvidia-smi -L
GPU 0: NVIDIA GeForce RTX 4090 (UUID: <REDACTED>)
GPU 1: NVIDIA GeForce RTX 2080 SUPER (UUID: <REDACTED>)

You can check all the identifiers that have been generated for your auto-detected hardware by checking the contents of the /var/run/cdi/nvidia-container-toolkit.json file:

$ nix run nixpkgs#jq -- -r '.devices[].name' < /var/run/cdi/nvidia-container-toolkit.json
0
1
all
Specifying what devices to expose to the container

You can choose what devices are exposed to your containers by using the identifier on the generated CDI specification. Like follows:

$ podman run --rm -it --device=nvidia.com/gpu=0 ubuntu:latest nvidia-smi -L
GPU 0: NVIDIA GeForce RTX 4090 (UUID: <REDACTED>)

You can repeat the --device argument as many times as necessary if you have multiple GPU’s and you want to pick up which ones to expose to the container:

$ podman run --rm -it --device=nvidia.com/gpu=0 --device=nvidia.com/gpu=1 ubuntu:latest nvidia-smi -L
GPU 0: NVIDIA GeForce RTX 4090 (UUID: <REDACTED>)
GPU 1: NVIDIA GeForce RTX 2080 SUPER (UUID: <REDACTED>)

Note

By default, the NVIDIA Container Toolkit will use the GPU index to identify specific devices. You can change the way to identify what devices to expose by using the hardware.nvidia-container-toolkit.device-name-strategy NixOS attribute.

Using docker-compose

It’s possible to expose GPUs to a docker-compose environment as well. With a docker-compose.yaml file like follows:

services:
  some-service:
    image: ubuntu:latest
    command: sleep infinity
    deploy:
      resources:
        reservations:
          devices:
          - driver: cdi
            device_ids:
            - nvidia.com/gpu=all

In the same manner, you can pick specific devices that will be exposed to the container:

services:
  some-service:
    image: ubuntu:latest
    command: sleep infinity
    deploy:
      resources:
        reservations:
          devices:
          - driver: cdi
            device_ids:
            - nvidia.com/gpu=0
            - nvidia.com/gpu=1

Contributing

Warning

This section of the docs is still very much in progress. Feedback is welcome in GitHub Issues tagging @NixOS/cuda-maintainers or on Matrix.

Package set maintenance

The CUDA Toolkit is a suite of CUDA libraries and software meant to provide a development environment for CUDA-accelerated applications. Until the release of CUDA 11.4, NVIDIA had only made the CUDA Toolkit available as a multi-gigabyte runfile installer. From CUDA 11.4 and onwards, NVIDIA has also provided CUDA redistributables (“CUDA-redist”): individually packaged CUDA Toolkit components meant to facilitate redistribution and inclusion in downstream projects. These packages are available in the cudaPackages package set.

While the monolithic CUDA Toolkit runfile installer is no longer provided, cudaPackages.cudatoolkit provides a symlinkJoin-ed approximation which common libraries. The use of cudaPackages.cudatoolkit is discouraged: all new projects should use the CUDA redistributables available in cudaPackages instead, as they are much easier to maintain and update.

Updating redistributables

Whenever a new version of a redistributable manifest is made available:

  1. Check the corresponding README.md in pkgs/development/cuda-modules/_cuda/manifests for the URL to use when vendoring manifests.

  2. Update the manifest version used in construction of each CUDA package set in pkgs/top-level/cuda-packages.nix.

  3. Update package expressions in pkgs/development/cuda-modules/packages.

Updating package expressions amounts to:

  • adding fixes conditioned on newer releases, like added or removed dependencies

  • adding package expressions for new packages

  • updating passthru.brokenConditions and passthru.badPlatformsConditions with various constraints, (e.g., new releases removing support for various architectures)

Updating supported compilers and GPUs
  1. Update nvccCompatibilities in pkgs/development/cuda-modules/_cuda/db/bootstrap/nvcc.nix to include the newest release of NVCC, as well as any newly supported host compilers.

  2. Update cudaCapabilityToInfo in pkgs/development/cuda-modules/_cuda/db/bootstrap/cuda.nix to include any new GPUs supported by the new release of CUDA.

Updating the CUDA package set

Note

Changing the default CUDA package set should occur in a separate PR, allowing time for additional testing.

Warning

As described in Using cudaPackages.pkgs, the current implementation fix for package set leakage involves creating a new instance for each non-default CUDA package sets. As such, We should limit the number of CUDA package sets which have recurseForDerivations set to true: lib.recurseIntoAttrs should only be applied to the default CUDA package set.

  1. Include a new cudaPackages_<major>_<minor> package set in pkgs/top-level/cuda-packages.nix and inherit it in pkgs/top-level/all-packages.nix.

  2. Successfully build the closure of the new package set, updating expressions in pkgs/development/cuda-modules/packages as needed. Below are some common failures:

Unable to …During …ReasonSolutionNote
Find headersconfigurePhase or buildPhaseMissing dependency on a dev outputAdd the missing dependencyThe dev output typically contains the headers
Find librariesconfigurePhaseMissing dependency on a dev outputAdd the missing dependencyThe dev output typically contains CMake configuration files
Find librariesbuildPhase or patchelfMissing dependency on a lib or static outputAdd the missing dependencyThe lib or static output typically contains the libraries

Note

Two utility derivations ease testing updates to the package set:

  • cudaPackages.tests.redists-unpacked: the src of each redistributable package unpacked and symlinkJoin-ed

  • cudaPackages.tests.redists-installed: each output of each redistributable package symlinkJoin-ed

Failure to run the resulting binary is typically the most challenging to diagnose, as it may involve a combination of the aforementioned issues. This type of failure typically occurs when a library attempts to load or open a library it depends on that it does not declare in its DT_NEEDED section. Try the following debugging steps:

  1. First ensure that dependencies are patched with autoAddDriverRunpath.

  2. Failing that, try running the application with nixGL or a similar wrapper tool.

  3. If that works, it likely means that the application is attempting to load a library that is not in the RPATH or RUNPATH of the binary.

Writing tests

Caution

The existence of passthru.testers and passthru.tests should be considered an implementation detail – they are not meant to be a public or stable interface.

In general, there are two attribute sets in passthru that are used to build and run tests for CUDA packages: passthru.testers and passthru.tests. Each attribute set may contain an attribute set named cuda, which contains CUDA-specific derivations. The cuda attribute set is used to separate CUDA-specific derivations from those which support multiple implementations (e.g., OpenCL, ROCm, etc.) or have different licenses. For an example of such generic derivations, see the magma package.

Note

Derivations are nested under the cuda attribute due to an OfBorg quirk: if evaluation fails (e.g., because of unfree licenses), the entire enclosing attribute set is discarded. This prevents other attributes in the set from being discovered, evaluated, or built.

passthru.testers

Attributes added to passthru.testers are derivations which produce an executable which runs a test. The produced executable should:

  • Take care to set up the environment, make temporary directories, and so on.

  • Be registered as the derivation’s meta.mainProgram so that it can be run directly.

Note

Testers which always require CUDA should be placed in passthru.testers.cuda, while those which are generic should be placed in passthru.testers.

The passthru.testers attribute set allows running tests outside the Nix sandbox. There are a number of reasons why this is useful, since such a test:

  • Can be run on non-NixOS systems, when wrapped with utilities like nixGL or nix-gl-host.

  • Has network access patterns which are difficult or impossible to sandbox.

  • Is free to produce output which is not deterministic, such as timing information.

passthru.tests

Attributes added to passthru.tests are derivations which run tests inside the Nix sandbox. Tests should:

  • Use the executables produced by passthru.testers, where possible, to avoid duplication of test logic.

  • Include requiredSystemFeatures = [ "cuda" ];, possibly conditioned on the value of cudaSupport if they are generic, to ensure that they are only run on systems exposing a CUDA-capable GPU.

Note

Tests which always require CUDA should be placed in passthru.tests.cuda, while those which are generic should be placed in passthru.tests.

This is useful for tests which are deterministic (e.g., checking exit codes) and which can be provided with all necessary resources in the sandbox.

Cue (Cuelang)

Cuelang is a language to:

  • describe schemas and validate backward-compatibility

  • generate code and schemas in various formats (e.g. JSON Schema, OpenAPI)

  • do configuration akin to Dhall Lang

  • perform data validation

Cuelang schema quick start

Cuelang schemas are similar to JSON, here is a quick cheatsheet:

  • Default types includes: null, string, bool, bytes, number, int, float, lists as [...T] where T is a type.

  • All structures, defined by: myStructName: { <fields> } are open – they accept fields which are not specified.

  • Closed structures can be built by doing myStructName: close({ <fields> }) – they are strict in what they accept.

  • #X are definitions, referenced definitions are recursively closed, i.e. all its children structures are closed.

  • & operator is the unification operator (similar to a type-level merging operator), | is the disjunction operator (similar to a type-level union operator).

  • Values are types, i.e. myStruct: { a: 3 } is a valid type definition that only allows 3 as value.

  • Read https://cuelang.org/docs/concepts/logic/ to learn more about the semantics.

  • Read https://cuelang.org/docs/references/spec/ to learn about the language specification.

writeCueValidator

Nixpkgs provides a pkgs.writeCueValidator helper, which will write a validation script based on the provided Cuelang schema.

Here is an example:

pkgs.writeCueValidator (pkgs.writeText "schema.cue" ''
  #Def1: {
    field1: string
  }
'') { document = "#Def1"; }
  • The first parameter is the Cue schema file.

  • The second parameter is an options parameter, currently, only: document can be passed.

document : match your input data against this fragment of structure or definition, e.g. you may use the same schema file but different documents based on the data you are validating.

Another example, given the following validator.nix :

{
  pkgs ? import <nixpkgs> { },
}:
let
  genericValidator =
    version:
    pkgs.writeCueValidator (pkgs.writeText "schema.cue" ''
      #Version1: {
        field1: string
      }
      #Version2: #Version1 & {
        field1: "unused"
      }'') { document = "#Version${toString version}"; };
in
{
  validateV1 = genericValidator 1;
  validateV2 = genericValidator 2;
}

The result is a script that will validate the file you pass as the first argument against the schema you provided writeCueValidator.

It can be any format that cue vet supports, i.e. YAML or JSON for example.

Here is an example, named example.json, given the following JSON:

{ "field1": "abc" }

You can run the result script (named validate) as the following:

$ nix-build validator.nix
$ ./result example.json
$ ./result-2 example.json
field1: conflicting values "unused" and "abc":
    ./example.json:1:13
    ../../../../../../nix/store/v64dzx3vr3glpk0cq4hzmh450lrwh6sg-schema.cue:5:11
$ sed -i 's/"abc"/3/' example.json
$ ./result example.json
field1: conflicting values 3 and string (mismatched types int and string):
    ./example.json:1:13
    ../../../../../../nix/store/v64dzx3vr3glpk0cq4hzmh450lrwh6sg-schema.cue:5:11

Known limitations

  • The script will enforce concrete values and will not accept lossy transformations (strictness). You can add these options if you need them.

Dart

Dart applications

The function buildDartApplication builds Dart applications managed with pub.

It fetches its Dart dependencies automatically through pub2nix, and (through a series of hooks) builds and installs the executables specified in the pubspec file. The hooks can be used in other derivations, if needed. The phases can also be overridden to do something different from installing binaries.

If you are packaging a Flutter desktop application, use buildFlutterApplication instead.

pubspecLock is the parsed pubspec.lock file. pub2nix uses this to download required packages. This can be converted to JSON from YAML with something like yq . pubspec.lock, and then read by Nix.

Alternatively, autoPubspecLock can be used instead, and set to a path to a regular pubspec.lock file. This relies on import-from-derivation, and is not permitted in Nixpkgs, but can be useful at other times.

Warning

When using autoPubspecLock with a local source directory, make sure to use a concatenation operator (e.g. autoPubspecLock = src + "/pubspec.lock";), and not string interpolation.

String interpolation will copy your entire source directory to the Nix store and use its store path, meaning that unrelated changes to your source tree will cause the generated pubspec.lock derivation to rebuild!

If the package has Git package dependencies, the hashes must be provided in the gitHashes set. If a hash is missing, an error message prompting you to add it will be shown.

The dart commands run can be overridden through pubGetScript and dartCompileCommand; you can also add flags using dartCompileFlags or dartJitFlags.

Dart supports multiple outputs types; you can choose between them using dartOutputType (defaults to exe). If you want to override the binaries path or the source path they come from, you can use dartEntryPoints. Outputs that require a runtime will automatically be wrapped with the relevant runtime (dartaotruntime for aot-snapshot, dart run for jit-snapshot and kernel, node for js); this can be overridden through dartRuntimeCommand.

{
  lib,
  buildDartApplication,
  fetchFromGitHub,
}:

buildDartApplication (finalAttrs: {
  pname = "dart-sass";
  version = "1.62.1";

  src = fetchFromGitHub {
    owner = "sass";
    repo = "dart-sass";
    tag = finalAttrs.version;
    hash = "sha256-U6enz8yJcc4Wf8m54eYIAnVg/jsGi247Wy8lp1r1wg4=";
  };

  pubspecLock = lib.importJSON ./pubspec.lock.json;
})

Patching dependencies

Some Dart packages require patches or build environment changes. Package derivations can be customised with the customSourceBuilders argument.

A collection of such customisations can be found in Nixpkgs, in the development/compilers/dart/package-source-builders directory.

This allows fixes for packages to be shared between all applications that use them. It is strongly recommended to add to this collection instead of including fixes in your application derivation itself.

Running executables from dev_dependencies

Many Dart applications require executables from the dev_dependencies section in pubspec.yaml to be run before building them.

This can be done in preBuild, in one of two ways:

  1. Packaging the tool with buildDartApplication, adding it to Nixpkgs, and running it like any other application

  2. Running the tool from the package cache

Of these methods, the first is recommended when using a tool that does not need to be of a specific version.

For the second method, the packageRun function from the dartConfigHook can be used. This is an alternative to dart run that does not rely on Pub.

e.g., for build_runner:

packageRun build_runner build

Do not use dart run <package_name>, as this will attempt to download dependencies with Pub.

Usage with nix-shell

Using dependencies from the Nix store

As buildDartApplication provides dependencies instead of pub get, Dart needs to be explicitly told where to find them.

Run the following commands in the source directory to configure Dart appropriately. Do not use pub after doing so; it will download the dependencies itself and overwrite these changes.

cp --no-preserve=all "$pubspecLockFilePath" pubspec.lock
mkdir -p .dart_tool && cp --no-preserve=all "$packageConfig" .dart_tool/package_config.json

Flutter applications

The function buildFlutterApplication builds Flutter applications.

See the Dart documentation for more details on required files and arguments.

flutter in Nixpkgs always points to flutterPackages.stable, which is the latest packaged version. To avoid unforeseen breakage during upgrade, packages in Nixpkgs should use a specific flutter version, such as flutter335 and flutter338, instead of using flutter directly.

{ flutter335, fetchFromGitHub }:

flutter335.buildFlutterApplication (finalAttrs: {
  pname = "firmware-updater";
  version = "0-unstable-2025-09-09";

  # To build for the Web, use the targetFlutterPlatform argument.
  # targetFlutterPlatform = "web";

  src = fetchFromGitHub {
    owner = "canonical";
    repo = "firmware-updater";
    rev = "402e97254b9d63c8d962c46724995e377ff922c8";
    hash = "sha256-nQn5mlgNj157h++67+mhez/F1ALz4yY+bxiGsi0/xX8=";
    fetchSubmodules = true;
  };

  pubspecLock = lib.importJSON ./pubspec.lock.json;

  sourceRoot = "${finalAttrs.src.name}/apps/firmware_updater";

  gitHashes.fwupd = "sha256-l/+HrrJk1mE2Mrau+NmoQ7bu9qhHU6wX68+m++9Hjd4=";
})

Usage with nix-shell

Flutter-specific nix-shell usage notes are included here. See the Dart documentation for general nix-shell instructions.

Entering the shell

By default, dependencies for only the targetFlutterPlatform are available in the build environment. This is useful for keeping closures small but can be problematic during development. It’s common, for example, to build Web apps for Linux during development to take advantage of native features such as stateful hot reload.

To enter a shell with all the usual target platforms available, use the multiShell attribute.

e.g. nix-shell '<nixpkgs>' -A fluffychat-web.multiShell.

Dhall

The Nixpkgs support for Dhall assumes some familiarity with Dhall’s language support for importing Dhall expressions, which is documented here:

Remote imports

Nixpkgs bypasses Dhall’s support for remote imports using Dhall’s semantic integrity checks. Specifically, any Dhall import can be protected by an integrity check like:

https://prelude.dhall-lang.org/v20.1.0/package.dhall
  sha256:26b0ef498663d269e4dc6a82b0ee289ec565d683ef4c00d0ebdd25333a5a3c98

… and if the import is cached, then the interpreter will load the import from the cache instead of fetching the URL.

Nixpkgs uses this trick to add all of a Dhall expression’s dependencies into the cache so that the Dhall interpreter never needs to resolve any remote URLs. In fact, Nixpkgs uses a Dhall interpreter with remote imports disabled when packaging Dhall expressions to enforce that the interpreter never resolves a remote import. This means that Nixpkgs only supports building Dhall expressions if all of their remote imports are protected by semantic integrity checks.

Instead of remote imports, Nixpkgs uses Nix to fetch remote Dhall code. For example, the Prelude Dhall package uses pkgs.fetchFromGitHub to fetch the dhall-lang repository containing the Prelude. Relying exclusively on Nix to fetch Dhall code ensures that Dhall packages built using Nix remain pure and also behave well when built within a sandbox.

Packaging a Dhall expression from scratch

We can illustrate how Nixpkgs integrates Dhall by beginning from the following trivial Dhall expression with one dependency (the Prelude):

-- ./true.dhall

let Prelude = https://prelude.dhall-lang.org/v20.1.0/package.dhall

in  Prelude.Bool.not False

As written, this expression cannot be built using Nixpkgs because the expression does not protect the Prelude import with a semantic integrity check, so the first step is to freeze the expression using dhall freeze, like this:

$ dhall freeze --inplace ./true.dhall

… which gives us:

-- ./true.dhall

let Prelude =
      https://prelude.dhall-lang.org/v20.1.0/package.dhall
        sha256:26b0ef498663d269e4dc6a82b0ee289ec565d683ef4c00d0ebdd25333a5a3c98

in  Prelude.Bool.not False

To package that expression, we create a ./true.nix file containing the following specification for the Dhall package:

# ./true.nix

{ buildDhallPackage, Prelude }:

buildDhallPackage {
  name = "true";
  code = ./true.dhall;
  dependencies = [ Prelude ];
  source = true;
}

… and we complete the build by incorporating that Dhall package into the pkgs.dhallPackages hierarchy using an overlay, like this:

# ./example.nix

let
  nixpkgs = fetchTarball {
    url = "https://github.com/NixOS/nixpkgs/archive/94b2848559b12a8ed1fe433084686b2a81123c99.tar.gz";
    hash = "sha256-B4Q3c6IvTLg3Q92qYa8y+i4uTaphtFdjp+Ir3QQjdN0=";
  };

  dhallOverlay = self: super: { true = self.callPackage ./true.nix { }; };

  overlay = self: super: {
    dhallPackages = super.dhallPackages.override (old: {
      overrides = self.lib.composeExtensions (old.overrides or (_: _: { })) dhallOverlay;
    });
  };

  pkgs = import nixpkgs {
    config = { };
    overlays = [ overlay ];
  };

in
pkgs

… which we can then build using this command:

$ nix build --file ./example.nix dhallPackages.true

Contents of a Dhall package

The above package produces the following directory tree:

$ tree -a ./result
result
├── .cache
│   └── dhall
│       └── 122027abdeddfe8503496adeb623466caa47da5f63abd2bc6fa19f6cfcb73ecfed70
├── binary.dhall
└── source.dhall

… where:

  • source.dhall contains the result of interpreting our Dhall package:

    $ cat ./result/source.dhall
    True
    
  • The .cache subdirectory contains one binary cache product encoding the same result as source.dhall:

    $ dhall decode < ./result/.cache/dhall/122027abdeddfe8503496adeb623466caa47da5f63abd2bc6fa19f6cfcb73ecfed70
    True
    
  • binary.dhall contains a Dhall expression which handles fetching and decoding the same cache product:

    $ cat ./result/binary.dhall
    missing sha256:27abdeddfe8503496adeb623466caa47da5f63abd2bc6fa19f6cfcb73ecfed70
    $ cp -r ./result/.cache .cache
    
    $ chmod -R u+w .cache
    
    $ XDG_CACHE_HOME=.cache dhall --file ./result/binary.dhall
    True
    

The source.dhall file is only present for packages that specify source = true;. By default, Dhall packages omit the source.dhall in order to conserve disk space when they are used exclusively as dependencies. For example, if we build the Prelude package it will only contain the binary encoding of the expression:

$ nix build --file ./example.nix dhallPackages.Prelude

$ tree -a result
result
├── .cache
│   └── dhall
│       └── 122026b0ef498663d269e4dc6a82b0ee289ec565d683ef4c00d0ebdd25333a5a3c98
└── binary.dhall

2 directories, 2 files

Typically, you only specify source = true; for the top-level Dhall expression of interest (such as our example true.nix Dhall package). However, if you wish to specify source = true for all Dhall packages, then you can amend the Dhall overlay like this:

{
  dhallOverrides = self: super: {
    # Enable source for all Dhall packages
    buildDhallPackage = args: super.buildDhallPackage (args // { source = true; });

    true = self.callPackage ./true.nix { };
  };
}

… and now the Prelude will contain the fully decoded result of interpreting the Prelude:

$ nix build --file ./example.nix dhallPackages.Prelude

$ tree -a result
result
├── .cache
│   └── dhall
│       └── 122026b0ef498663d269e4dc6a82b0ee289ec565d683ef4c00d0ebdd25333a5a3c98
├── binary.dhall
└── source.dhall

$ cat ./result/source.dhall
{ Bool =
  { and =
      \(_ : List Bool) ->
        List/fold Bool _ Bool (\(_ : Bool) -> \(_ : Bool) -> _@1 && _) True
  , build = \(_ : Type -> _ -> _@1 -> _@2) -> _ Bool True False
  , even =
      \(_ : List Bool) ->
        List/fold Bool _ Bool (\(_ : Bool) -> \(_ : Bool) -> _@1 == _) True
  , fold =
      \(_ : Bool) ->
…

Packaging functions

We already saw an example of using buildDhallPackage to create a Dhall package from a single file, but most Dhall packages consist of more than one file and there are two derived utilities that you may find more useful when packaging multiple files:

  • buildDhallDirectoryPackage - build a Dhall package from a local directory

  • buildDhallGitHubPackage - build a Dhall package from a GitHub repository

The buildDhallPackage is the lowest-level function and accepts the following arguments:

  • name: The name of the derivation

  • dependencies: Dhall dependencies to build and cache ahead of time

  • code: The top-level expression to build for this package

    Note that the code field accepts an arbitrary Dhall expression. You’re not limited to just a file.

  • source: Set to true to include the decoded result as source.dhall in the build product, at the expense of requiring more disk space

  • documentationRoot: Set to the root directory of the package if you want dhall-docs to generate documentation underneath the docs subdirectory of the build product

The buildDhallDirectoryPackage is a higher-level function implemented in terms of buildDhallPackage that accepts the following arguments:

  • name: Same as buildDhallPackage

  • dependencies: Same as buildDhallPackage

  • source: Same as buildDhallPackage

  • src: The directory containing Dhall code that you want to turn into a Dhall package

  • file: The top-level file (package.dhall by default) that is the entry point to the rest of the package

  • document: Set to true to generate documentation for the package

The buildDhallGitHubPackage is another higher-level function implemented in terms of buildDhallPackage that accepts the following arguments:

  • name: Same as buildDhallPackage

  • dependencies: Same as buildDhallPackage

  • source: Same as buildDhallPackage

  • owner: The owner of the repository

  • repo: The repository name

  • rev: The desired revision (or branch, or tag)

  • directory: The subdirectory of the Git repository to package (if a directory other than the root of the repository)

  • file: The top-level file (${directory}/package.dhall by default) that is the entry point to the rest of the package

  • document: Set to true to generate documentation for the package

Additionally, buildDhallGitHubPackage accepts the same arguments as fetchFromGitHub, such as hash or fetchSubmodules.

dhall-to-nixpkgs

You can use the dhall-to-nixpkgs command-line utility to automate packaging Dhall code. For example:

$ nix-shell -p haskellPackages.dhall-nixpkgs nix-prefetch-git
[nix-shell]$ dhall-to-nixpkgs github https://github.com/Gabriella439/dhall-semver.git
{ buildDhallGitHubPackage, Prelude }:
  buildDhallGitHubPackage {
    name = "dhall-semver";
    githubBase = "github.com";
    owner = "Gabriella439";
    repo = "dhall-semver";
    rev = "2d44ae605302ce5dc6c657a1216887fbb96392a4";
    fetchSubmodules = false;
    hash = "sha256-n0nQtswVapWi/x7or0O3MEYmAkt/a1uvlOtnje6GGnk=";
    directory = "";
    file = "package.dhall";
    source = false;
    document = false;
    dependencies = [ (Prelude.overridePackage { file = "package.dhall"; }) ];
    }

Note

nix-prefetch-git is added to the nix-shell -p invocation above, because it has to be in $PATH for dhall-to-nixpkgs to work.

The utility takes care of automatically detecting remote imports and converting them to package dependencies. You can also use the utility on local Dhall directories, too:

$ dhall-to-nixpkgs directory ~/proj/dhall-semver
{ buildDhallDirectoryPackage, Prelude }:
  buildDhallDirectoryPackage {
    name = "proj";
    src = ~/proj/dhall-semver;
    file = "package.dhall";
    source = false;
    document = false;
    dependencies = [ (Prelude.overridePackage { file = "package.dhall"; }) ];
    }

Remote imports as fixed-output derivations

dhall-to-nixpkgs has the ability to fetch and build remote imports as fixed-output derivations by using their Dhall integrity check. This is sometimes easier than manually packaging all remote imports.

This can be used like the following:

$ dhall-to-nixpkgs directory --fixed-output-derivations ~/proj/dhall-semver
{ buildDhallDirectoryPackage, buildDhallUrl }:
  buildDhallDirectoryPackage {
    name = "proj";
    src = ~/proj/dhall-semver;
    file = "package.dhall";
    source = false;
    document = false;
    dependencies = [
      (buildDhallUrl {
        url = "https://prelude.dhall-lang.org/v17.0.0/package.dhall";
        hash = "sha256-ENs8kZwl6QRoM9+Jeo/+JwHcOQ+giT2VjDQwUkvlpD4=";
        dhallHash = "sha256:10db3c919c25e9046833df897a8ffe2701dc390fa0893d958c3430524be5a43e";
        })
      ];
    }

Here, dhall-semver’s Prelude dependency is fetched and built with the buildDhallUrl helper function, instead of being passed in as a function argument.

Overriding dependency versions

Suppose that we change our true.dhall example expression to depend on an older version of the Prelude (19.0.0):

-- ./true.dhall

let Prelude =
      https://prelude.dhall-lang.org/v19.0.0/package.dhall
        sha256:eb693342eb769f782174157eba9b5924cf8ac6793897fc36a31ccbd6f56dafe2

in  Prelude.Bool.not False

If we try to rebuild that expression the build will fail:

$ nix build --file ./example.nix dhallPackages.true
builder for '/nix/store/0f1hla7ff1wiaqyk1r2ky4wnhnw114fi-true.drv' failed with exit code 1; last 10 log lines:

  Dhall was compiled without the 'with-http' flag.

  The requested URL was: https://prelude.dhall-lang.org/v19.0.0/package.dhall


  4│       https://prelude.dhall-lang.org/v19.0.0/package.dhall
  5│         sha256:eb693342eb769f782174157eba9b5924cf8ac6793897fc36a31ccbd6f56dafe2

  /nix/store/rsab4y99h14912h4zplqx2iizr5n4rc2-true.dhall:4:7
[1 built (1 failed), 0.0 MiB DL]
error: build of '/nix/store/0f1hla7ff1wiaqyk1r2ky4wnhnw114fi-true.drv' failed

… because the default Prelude selected by Nixpkgs revision 94b2848559b12a8ed1fe433084686b2a81123c99 is version 20.1.0, which doesn’t have the same integrity check as version 19.0.0. This means that version 19.0.0 is not cached, and the interpreter is not allowed to fall back to importing the URL.

However, we can override the default Prelude version by using dhall-to-nixpkgs to create a Dhall package for our desired Prelude:

$ dhall-to-nixpkgs github https://github.com/dhall-lang/dhall-lang.git \
    --name Prelude \
    --directory Prelude \
    --rev v19.0.0 \
    > Prelude.nix

… and then referencing that package in our Dhall overlay, by either overriding the Prelude globally for all packages, like this:

{
  dhallOverrides = self: super: {
    true = self.callPackage ./true.nix { };

    Prelude = self.callPackage ./Prelude.nix { };
  };
}

… or selectively overriding the Prelude dependency for just the true package, like this:

{
  dhallOverrides = self: super: {
    true = self.callPackage ./true.nix {
      Prelude = self.callPackage ./Prelude.nix { };
    };
  };
}

Overrides

You can override any of the arguments to buildDhallGitHubPackage or buildDhallDirectoryPackage using the overridePackage attribute of a package. For example, suppose we wanted to selectively enable source = true just for the Prelude. We can do that like this:

{
  dhallOverrides = self: super: {
    Prelude = super.Prelude.overridePackage { source = true; };

    # ...
  };
}

D (Dlang)

Nixpkgs provides multiple D compilers such as ldc and dmd. These can be used like any other package during build time.

However, Nixpkgs provides a build helper for compiling packages using the dub package manager.

Here’s an example:

{
  lib,
  buildDubPackage,
  fetchFromGitHub,
  ncurses,
  zlib,
}:

buildDubPackage rec {
  pname = "btdu";
  version = "0.5.1";

  src = fetchFromGitHub {
    owner = "CyberShadow";
    repo = "btdu";
    tag = "v${version}";
    hash = "sha256-3sSZq+5UJH02IO0Y1yL3BLHDb4lk8k6awb5ZysBQciE=";
  };

  # generated by dub-to-nix, see below
  dubLock = ./dub-lock.json;

  buildInputs = [
    ncurses
    zlib
  ];

  installPhase = ''
    runHook preInstall
    install -Dm755 btdu -t $out/bin
    runHook postInstall
  '';
}

Note that you need to define installPhase because dub doesn’t know where files should go in $out.

Also note that running dub test is disabled by default. You can enable it by setting doCheck = true.

Lockfiles

Nixpkgs has its own lockfile format for dub dependencies, because dub’s official “lockfile” format (dub.selections.json) is not hash-based.

A lockfile can be generated using the dub-to-nix helper package.

  • Firstly, install dub-to-nix into your shell session by running nix-shell -p dub-to-nix.

  • Then navigate to the root of the source of the program you want to package.

  • Finally, run dub-to-nix, and it will print the lockfile to stdout. You can pipe stdout into a text file or just copy the output manually into a file.

buildDubPackage parameters

The buildDubPackage function takes an attrset of parameters that are passed on to stdenv.mkDerivation.

The following parameters are specific to buildDubPackage:

  • dubLock: A lockfile generated by dub-to-nix from the source of the package. Can be either a path to the file, or an attrset already parsed with lib.importJSON. The latter useful if the package uses dub dependencies not already in the lockfile. (e.g. if the package calls dub run some-dub-package manually)

  • dubBuildType ? "release": The build type to pass to dub build as a value for the --build= flag.

  • dubFlags ? []: The flags to pass to dub build and dub test.

  • dubBuildFlags ? []: The flags to pass to dub build.

  • dubTestFlags ? []: The flags to pass to dub test.

  • compiler ? ldc: The D compiler to be used by dub.

Dotnet

Local Development Workflow

For local development, it’s recommended to use nix-shell to create a dotnet environment:

# shell.nix
with import <nixpkgs> { };

mkShell {
  name = "dotnet-env";
  packages = [ dotnet-sdk ];
}

Using many sdks in a workflow

It’s very likely that more than one sdk will be needed on a given project. Dotnet provides several different frameworks (E.g dotnetcore, aspnetcore, etc.) as well as many versions for a given framework. Normally, dotnet is able to fetch a framework and install it relative to the executable. However, this would mean writing to the nix store in nixpkgs, which is read-only. To support the many-sdk use case, one can compose an environment using dotnetCorePackages.combinePackages:

with import <nixpkgs> { };

mkShell {
  name = "dotnet-env";
  packages = [
    (
      with dotnetCorePackages;
      combinePackages [
        sdk_8_0
        sdk_9_0
      ]
    )
  ];
}

This will produce a dotnet installation that has the dotnet 8.0 9.0 sdk. The first sdk listed will have its cli utility present in the resulting environment. Example info output:

$ dotnet --info
.NET SDK:
 Version:           9.0.100
 Commit:            59db016f11
 Workload version:  9.0.100-manifests.3068a692
 MSBuild version:   17.12.7+5b8665660

Runtime Environment:
 OS Name:     nixos
 OS Version:  25.05
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /nix/store/a03c70i7x6rjdr6vikczsp5ck3v6rixh-dotnet-sdk-9.0.100/share/dotnet/sdk/9.0.100/

.NET workloads installed:
There are no installed workloads to display.
Configured to use loose manifests when installing new manifests.

Host:
  Version:      9.0.0
  Architecture: x64
  Commit:       9d5a6a9aa4

.NET SDKs installed:
  8.0.404 [/nix/store/6wlrjiy10wg766490dcmp6x64zb1vc8j-dotnet-core-combined/share/dotnet/sdk]
  9.0.100 [/nix/store/6wlrjiy10wg766490dcmp6x64zb1vc8j-dotnet-core-combined/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 8.0.11 [/nix/store/6wlrjiy10wg766490dcmp6x64zb1vc8j-dotnet-core-combined/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 9.0.0 [/nix/store/6wlrjiy10wg766490dcmp6x64zb1vc8j-dotnet-core-combined/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 8.0.11 [/nix/store/6wlrjiy10wg766490dcmp6x64zb1vc8j-dotnet-core-combined/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 9.0.0 [/nix/store/6wlrjiy10wg766490dcmp6x64zb1vc8j-dotnet-core-combined/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

dotnet-sdk vs dotnetCorePackages.sdk

The dotnetCorePackages.sdk_X_Y is preferred over the old dotnet-sdk as both major and minor version are very important for a dotnet environment. If a given minor version isn’t present (or was changed), then this will likely break your ability to build a project.

dotnetCorePackages.sdk vs dotnetCorePackages.runtime vs dotnetCorePackages.aspnetcore

The dotnetCorePackages.sdk contains both a runtime and the full sdk of a given version. The runtime and aspnetcore packages are meant to serve as minimal runtimes to deploy alongside already built applications.

Packaging a Dotnet Application

To package Dotnet applications, you can use buildDotnetModule. This has similar arguments to stdenv.mkDerivation, with the following additions:

  • projectFile is used for specifying the dotnet project file, relative to the source root. These have .sln (entire solution) or .csproj (single project) file extensions. This can be a list of multiple projects as well. When omitted, will attempt to find and build the solution (.sln). If running into problems, make sure to set it to a file (or a list of files) with the .csproj extension - building applications as entire solutions is not fully supported by the .NET CLI.

  • nugetDeps should be a path to a JSON file, a path to a nix file (deprecated), a derivation, or a list of derivations. A deps.json file can be generated using the script attached to passthru.fetch-deps, which is the preferred method. All nugetDeps packages are added to buildInputs.

Note

For more detail about managing the deps.json file, see Generating and updating NuGet dependencies

  • packNupkg is used to pack project as a nupkg, and installs it to $out/share. If set to true, the derivation can be used as a dependency for another dotnet project by adding it to buildInputs.

  • buildInputs can be used to resolve ProjectReference project items. Referenced projects can be packed with buildDotnetModule by setting the packNupkg = true attribute and passing a list of derivations to buildInputs. Since we are sharing referenced projects as NuGets they must be added to csproj/fsproj files as PackageReference as well. For example, your project has a local dependency:

    <ProjectReference Include="../foo/bar.fsproj" />

To enable discovery through buildInputs you would need to add:

    <ProjectReference Include="../foo/bar.fsproj" />
    <PackageReference Include="bar" Version="*" Condition=" '$(ContinuousIntegrationBuild)'=='true' "/>
  • executables is used to specify which executables get wrapped to $out/bin, relative to $out/lib/$pname. If this is unset, all executables generated will get installed. If you do not want to install any, set this to []. This gets done in the preFixup phase.

  • runtimeDeps is used to wrap libraries into LD_LIBRARY_PATH. This is how dotnet usually handles runtime dependencies.

  • buildType is used to change the type of build. Possible values are Release, Debug, etc. By default, this is set to Release.

  • selfContainedBuild allows to enable the self-contained build flag. By default, it is set to false and generated applications have a dependency on the selected dotnet runtime. If enabled, the dotnet runtime is bundled into the executable and the built app has no dependency on .NET.

  • useAppHost will enable creation of a binary executable that runs the .NET application using the specified root. More info in Microsoft docs. Enabled by default.

  • useDotnetFromEnv will change the binary wrapper so that it uses the .NET from the environment. The runtime specified by dotnet-runtime is given as a fallback in case no .NET is installed in the user’s environment. This is most useful for .NET global tools and LSP servers, which often extend the .NET CLI and their runtime should match the user’s .NET runtime.

  • dotnet-sdk is useful in cases where you need to change what dotnet SDK is being used. You can also set this to the result of dotnetSdkPackages.combinePackages, if the project uses multiple SDKs to build.

  • dotnet-runtime is useful in cases where you need to change what dotnet runtime is being used. This can be either a regular dotnet runtime, or an aspnetcore.

  • testProjectFile is useful in cases where the regular project file does not contain the unit tests. It gets restored and build, but not installed. You may need to regenerate your nuget lockfile after setting this. Note that if set, only tests from this project are executed.

  • testFilters is used to disable running unit tests based on various filters. This gets passed as: dotnet test --filter "{}", with each filter being concatenated using "&".

  • disabledTests is used to disable running specific unit tests. This gets passed as: dotnet test --filter "FullyQualifiedName!={}", to ensure compatibility with all unit test frameworks.

  • dotnetRestoreFlags can be used to pass flags to dotnet restore.

  • dotnetBuildFlags can be used to pass flags to dotnet build.

  • dotnetTestFlags can be used to pass flags to dotnet test. Used only if doCheck is set to true.

  • dotnetInstallFlags can be used to pass flags to dotnet install.

  • dotnetPackFlags can be used to pass flags to dotnet pack. Used only if packNupkg is set to true.

  • dotnetFlags can be used to pass flags to all of the above phases.

When packaging a new application, you need to fetch its dependencies. Create an empty deps.json, set nugetDeps = ./deps.json, then run nix-build -A package.fetch-deps to generate a script that will build the lockfile for you.

Here is an example default.nix, using some of the previously discussed arguments:

{
  lib,
  buildDotnetModule,
  dotnetCorePackages,
  ffmpeg,
}:

let
  referencedProject = import ../../bar {
    # ...
  };
in
buildDotnetModule rec {
  pname = "someDotnetApplication";
  version = "0.1";

  src = ./.;

  projectFile = "src/project.sln";
  nugetDeps = ./deps.json; # see "Generating and updating NuGet dependencies" section for details

  buildInputs = [
    referencedProject
  ]; # `referencedProject` must contain `nupkg` in the folder structure.

  dotnet-sdk = dotnetCorePackages.sdk_8_0;
  dotnet-runtime = dotnetCorePackages.runtime_8_0;

  executables = [ "foo" ]; # This wraps "$out/lib/$pname/foo" to `$out/bin/foo`.
  executables = [ ]; # Don't install any executables.

  packNupkg = true; # This packs the project as "foo-0.1.nupkg" at `$out/share`.

  runtimeDeps = [ ffmpeg ]; # This will wrap ffmpeg's library path into `LD_LIBRARY_PATH`.
}

Keep in mind that you can tag the @NixOS/dotnet team for help and code review.

Dotnet global tools

.NET Global tools are a mechanism provided by the dotnet CLI to install .NET binaries from Nuget packages.

They can be installed either as a global tool for the entire system, or as a local tool specific to project.

The local installation is the easiest and works on NixOS in the same way as on other Linux distributions. See dotnet documentation to learn more.

The global installation method should also work most of the time. You have to remember to update the PATH value to the location the tools are installed to (the CLI will inform you about it during installation) and also set the DOTNET_ROOT value, so that the tool can find the .NET SDK package. You can find the path to the SDK by running nix eval --raw nixpkgs#dotnet-sdk (substitute the dotnet-sdk package for another if a different SDK version is needed).

This method is not recommended on NixOS, since it’s not declarative and involves installing binaries not made for NixOS, which will not always work.

The third, and preferred way, is packaging the tool into a Nix derivation.

Packaging Dotnet global tools

Dotnet global tools are standard .NET binaries, just made available through a special NuGet package. Therefore, they can be built and packaged like every .NET application, using buildDotnetModule.

If however the source is not available or difficult to build, the buildDotnetGlobalTool helper can be used, which will package the tool straight from its NuGet package.

This helper has the same arguments as buildDotnetModule, with a few differences:

  • pname and version are required, and will be used to find the NuGet package of the tool

  • nugetName can be used to override the NuGet package name that will be downloaded, if it’s different from pname

  • nugetHash is the hash of the fetched NuGet package. nugetSha256 is also supported, but not recommended. Set this to lib.fakeHash for the first build, and it will error out, giving you the proper hash. Also remember to update it during version updates (it will not error out if you just change the version while having a fetched package in /nix/store)

  • dotnet-runtime is set to dotnet-sdk by default. When changing this, remember that .NET tools fetched from NuGet require an SDK.

Here is an example of packaging pbm, an unfree binary without source available:

{ buildDotnetGlobalTool, lib }:

buildDotnetGlobalTool {
  pname = "pbm";
  version = "1.3.1";

  nugetHash = "sha256-ZG2HFyKYhVNVYd2kRlkbAjZJq88OADe3yjxmLuxXDUo=";

  meta = {
    homepage = "https://cmd.petabridge.com/index.html";
    changelog = "https://cmd.petabridge.com/articles/RELEASE_NOTES.html";
    license = lib.licenses.unfree;
    platforms = lib.platforms.linux;
  };
}

Generating and updating NuGet dependencies

When writing a new expression, you can use the generated fetch-deps script to initialise the lockfile. After setting nugetDeps to the desired location of the lockfile (e.g. ./deps.json), build the script with nix-build -A package.fetch-deps and then run the result. (When the root attr is your package, it’s simply nix-build -A fetch-deps.)

There is also a manual method: First, restore the packages to the out directory, ensure you have cloned the upstream repository and you are inside it.

$ dotnet restore --packages out
  Determining projects to restore...
  Restored /home/ggg/git-credential-manager/src/shared/Git-Credential-Manager/Git-Credential-Manager.csproj (in 1.21 sec).

Next, use the nuget-to-json tool provided in Nixpkgs to generate a lockfile to deps.json from the packages inside the out directory.

$ nuget-to-json out > deps.json

The nuget-to-json tool will generate an output similar to the one below

[
  {
    "pname": "Avalonia",
    "version": "11.1.3",
    "hash": "sha256-kz+k/vkuWoL0XBvRT8SadMOmmRCFk9W/J4k/IM6oYX0="
  },
  {
    "pname": "Avalonia.Angle.Windows.Natives",
    "version": "2.1.22045.20230930",
    "hash": "sha256-RxPcWUT3b/+R3Tu5E5ftpr5ppCLZrhm+OTsi0SwW3pc="
  },
  {
    "pname": "Avalonia.BuildServices",
    "version": "0.0.29",
    "hash": "sha256-WPHRMNowRnYSCh88DWNBCltWsLPyOfzXGzBqLYE7tRY="
  },
  // ...
  {
    "pname": "System.Runtime.CompilerServices.Unsafe",
    "version": "6.0.0",
    "hash": "sha256-bEG1PnDp7uKYz/OgLOWs3RWwQSVYm+AnPwVmAmcgp2I="
  },
  {
    "pname": "System.Security.Cryptography.ProtectedData",
    "version": "4.5.0",
    "hash": "sha256-Z+X1Z2lErLL7Ynt2jFszku6/IgrngO3V1bSfZTBiFIc="
  },
  {
    "pname": "Tmds.DBus.Protocol",
    "version": "0.16.0",
    "hash": "sha256-vKYEaa1EszR7alHj48R8G3uYArhI+zh2ZgiBv955E98="
  }
]

Finally, you move the deps.json file to the appropriate location to be used by nugetDeps, then you’re all set!

If you ever need to update the dependencies of a package, you instead do

  • nix-build -A package.fetch-deps to generate the update script for package

  • Run ./result to regenerate the lockfile to the path passed for nugetDeps (keep in mind if it can’t be resolved to a local path, the script will write to $1 or a temporary path instead)

  • Finally, ensure the correct file was written and the derivation can be built.

Emscripten

Emscripten: An LLVM-to-JavaScript Compiler

If you want to work with emcc, emconfigure and emmake as you are used to from Ubuntu and similar distributions,

nix-shell -p emscripten

A few things to note:

  • export EMCC_DEBUG=2 is nice for debugging

  • The build artifact cache in ~/.emscripten sometimes creates issues and needs to be removed from time to time

Examples

Let’s see two different examples from pkgs/top-level/emscripten-packages.nix:

  • pkgs.zlib.override

  • pkgs.buildEmscriptenPackage

A special requirement of the pkgs.buildEmscriptenPackage is the doCheck = true. This means each Emscripten package requires that a checkPhase is implemented.

  • Use export EMCC_DEBUG=2 from within a phase to get more detailed debug output what is going wrong.

  • The cache at ~/.emscripten requires to set HOME=$TMPDIR in individual phases. This makes compilation slower but also more deterministic.

Example 383. Using pkgs.zlib.override {}

This example uses zlib from Nixpkgs, but instead of compiling C to ELF it compiles C to JavaScript since we were using pkgs.zlib.override and changed stdenv to pkgs.emscriptenStdenv.

A few adaptions and hacks were put in place to make it work. One advantage is that when pkgs.zlib is updated, it will automatically update this package as well.

(pkgs.zlib.override { stdenv = pkgs.emscriptenStdenv; }).overrideAttrs (old: {
  buildInputs = old.buildInputs ++ [ pkg-config ];
  # we need to reset this setting!
  env = (old.env or { }) // {
    NIX_CFLAGS_COMPILE = "";
  };

  configurePhase = ''
    # FIXME: Some tests require writing at $HOME
    HOME=$TMPDIR
    runHook preConfigure

    #export EMCC_DEBUG=2
    emconfigure ./configure --prefix=$out --shared

    runHook postConfigure
  '';

  dontStrip = true;
  outputs = [ "out" ];

  buildPhase = ''
    runHook preBuild

    emmake make

    runHook postBuild
  '';

  installPhase = ''
    runHook preInstall

    emmake make install

    runHook postInstall
  '';

  checkPhase = ''
    runHook preCheck

    echo "================= testing zlib using node ================="

    echo "Compiling a custom test"
    set -x
    emcc -O2 -s EMULATE_FUNCTION_POINTER_CASTS=1 test/example.c -DZ_SOLO \
    libz.so.${old.version} -I . -o example.js

    echo "Using node to execute the test"
    ${pkgs.nodejs}/bin/node ./example.js

    set +x
    if [ $? -ne 0 ]; then
      echo "test failed for some reason"
      exit 1;
    else
      echo "it seems to work! very good."
    fi
    echo "================= /testing zlib using node ================="

    runHook postCheck
  '';

  postPatch = pkgs.lib.optionalString pkgs.stdenv.hostPlatform.isDarwin ''
    substituteInPlace configure \
      --replace-fail '/usr/bin/libtool' 'ar' \
      --replace-fail 'AR="libtool"' 'AR="ar"' \
      --replace-fail 'ARFLAGS="-o"' 'ARFLAGS="-r"'
  '';
})
Example 384. Using pkgs.buildEmscriptenPackage {}

This xmlmirror example features an Emscripten package that is defined completely from this context and no pkgs.zlib.override is used.

pkgs.buildEmscriptenPackage {
  pname = "xmlmirror";
  version = "1.2.3";

  buildInputs = [
    pkg-config
    autoconf
    automake
    libtool
    gnumake
    libxml2
    nodejs
    openjdk
    json_c
  ];

  nativeBuildInputs = [
    pkg-config
    writableTmpDirAsHomeHook
    zlib
  ];

  src = pkgs.fetchgit {
    url = "https://gitlab.com/odfplugfest/xmlmirror.git";
    rev = "4fd7e86f7c9526b8f4c1733e5c8b45175860a8fd";
    hash = "sha256-i+QgY+5PYVg5pwhzcDnkfXAznBg3e8sWH2jZtixuWsk=";
  };

  configurePhase = ''
    runHook preConfigure

    rm -f fastXmlLint.js*
    # a fix for ERROR:root:For asm.js, TOTAL_MEMORY must be a multiple of 16MB, was 234217728
    # https://gitlab.com/odfplugfest/xmlmirror/issues/8
    sed -e "s/TOTAL_MEMORY=234217728/TOTAL_MEMORY=268435456/g" -i Makefile.emEnv
    # https://github.com/kripken/emscripten/issues/6344
    # https://gitlab.com/odfplugfest/xmlmirror/issues/9
    sed -e "s/\$(JSONC_LDFLAGS) \$(ZLIB_LDFLAGS) \$(LIBXML20_LDFLAGS)/\$(JSONC_LDFLAGS) \$(LIBXML20_LDFLAGS) \$(ZLIB_LDFLAGS) /g" -i Makefile.emEnv
    # https://gitlab.com/odfplugfest/xmlmirror/issues/11
    sed -e "s/-o fastXmlLint.js/-s EXTRA_EXPORTED_RUNTIME_METHODS='[\"ccall\", \"cwrap\"]' -o fastXmlLint.js/g" -i Makefile.emEnv

    runHook postConfigure
  '';

  buildPhase = ''
    runHook preBuild

    make -f Makefile.emEnv

    runHook postBuild
  '';

  outputs = [
    "out"
    "doc"
  ];

  installPhase = ''
    runHook preInstall

    mkdir -p $out/share
    mkdir -p $doc/share/${name}

    cp Demo* $out/share
    cp -R codemirror-5.12 $out/share
    cp fastXmlLint.js* $out/share
    cp *.xsd $out/share
    cp *.js $out/share
    cp *.xhtml $out/share
    cp *.html $out/share
    cp *.json $out/share
    cp *.rng $out/share
    cp README.md $doc/share/${name}

    runHook postInstall
  '';

  checkPhase = ''
    runHook preCheck

    runHook postCheck
  '';
}


Debugging

Use nix-shell -I nixpkgs=/some/dir/nixpkgs -A emscriptenPackages.libz and from there you can go through the individual steps. This makes it easy to build a good unit test or list the files of the project.

  1. nix-shell -I nixpkgs=/some/dir/nixpkgs -A emscriptenPackages.libz

  2. cd /tmp/

  3. unpackPhase

  4. cd libz-1.2.3

  5. configurePhase

  6. buildPhase

  7. … happy hacking…

Factor

Development Environment

All Nix expressions for the Factor compiler and development environment can be found in pkgs/top-level/factor-packages.nix.

The default package factor-lang provides support for the built-in graphical user interface and a selected set of C library bindings, e.g., for sound and TLS connections. It also comes with the Fuel library for Emacs that provides an integrated development environment for developing Factor programs including access to the Factor runtime and online documentation.

For using less frequently used libraries that need additional bindings, you can override the factor-lang package and add more library bindings and/or binaries to its PATH. The package is defined in pkgs/development/compilers/factor-lang/wrapper.nix and provides several attributes for adding those:

  • extraLibs adds the packages’ /lib paths to the wrapper and adds all shared libraries to an ld.so cache such that they can be found dynamically by the Factor runtime.

  • binPackages does the same as extraLibs and additionally adds the packages to Factor’s PATH environment variable.

  • extraVocabs adds Factor vocabularies to the tree that are not part of the standard library. The packages must adhere to the default vocabulary root structure to be found.

  • guiSupport draws in all necessary graphical libraries to enable the Factor GUI. This should be set to true when considering building and running graphical applications with this Factor runtime (even if the Factor GUI is not used for programming). This argument is true by default.

  • enableDefaults can be deactivated to only wrap libraries that are named in extraLibs or binPackages. This reduces the runtime dependencies especially when shipping Factor applications.

The package also passes through several attributes listing the wrapped libraries and binaries, namely, extraLibs and binPackages as well as defaultLibs and defaultBins. Additionally, all runtimeLibs is the concatenation of all the above for the purpose of providing all necessary dynamic libraries as “propagatedBuildInputs”. Lastly, extraVocabs is passed through as is for stacked composition, and the fully composed vocabTree is passed through as a store path. This makes it easier for external plugins (e.g. for editors and IDEs) to refer to the Factor vocabulary roots.

factorPackages provides pre-configured Factor packages:

  • factorPackages.factor-lang is the default package with GUI support and several default library bindings (e.g. openssl, openal etc.).

  • factorPackages.factor-no-gui turns off GUI support while maintaining default library bindings.

  • factorPackages.factor-minimal comes with practically no additional library bindings and binaries and no GUI support.

  • factorPackages.factor-minimal-gui comes with no additional library bindings but includes GUI support.

Scaffolding and the work vocabulary root

Factor uses the concept of “scaffolding” to spin off a new vocabulary in a personal workspace rooted at the work vocabulary root. This concept does not scale very well, because it makes many assumptions which all turn out to be wrong at some point. In the current implementation, the work vocabulary root points to /var/lib/factor on the target machine. This can be suitable for a single-user system. Create the location and make it writable to your user. Then, you can use the scaffold-work word as instructed by many tutorials.

If you don’t like this approach, you can work around it by creating a ~/.factor-roots file in your home directory which contains the locations you desire to represent additional Factor vocabulary roots, one directory per line. Use scaffold-vocab to create your vocabularies in one of these additional roots. The online Factor documentation is extensive on how to use the scaffolding framework.

Packaging Factor Vocabularies

All Factor vocabularies that shall be added to a Factor environment via the extraVocabs attribute must adhere to the following directory scheme. Its top-level directory must be one (or multiple) of basis, core or extra. work is routed to /var/lib/factor and is not shipped nor referenced in the nix store, see the section on scaffolding. You should usually use extra, but you can use the other roots to overwrite built-in vocabularies. Be aware that vocabularies in core are part of the Factor image which the development environment is run from. This means the code in those vocabularies is not loaded from the sources, such that you need to call refresh-all to recompile and load the changed definitions. In these instances, it is advised to override the factor-unwrapped package directly, which compiles and packages the core Factor libraries into the default Factor image.

As per Factor convention, your vocabulary foo.factor must be in a directory of the same name in addition to one of the previously mentioned vocabulary roots, e.g. extra/foo/foo.factor.

All extra Factor vocabularies are registered in pkgs/top-level/factor-packages.nix and their package definitions usually live in development/compilers/factor-lang/vocabs/.

Package a vocabulary using the buildFactorVocab function. Its default installPhase takes care of installing it under out/lib/factor. It also understands the following special attributes:

  • vocabName is the path to the vocabulary to be installed. Defaults to pname.

  • vocabRoot is the vocabulary root to install the vocabulary under. Defaults to extra. Unless you know what you are doing, do not change it. Other readily understood vocabulary roots are core and basis, which allow you to modify the default Factor runtime environment with an external package.

  • extraLibs, extraVocabs, extraPaths have the same meaning as for applications. They have no immediate effect and are just passed through. When building factor-lang packages and Factor applications that use this respective vocabulary, these variables are evaluated and their paths added to the runtime environment.

The function understands several forms of source directory trees:

  1. Simple single-vocab projects with their Factor and supplementary files directly in the project root. All .factor and .txt files are copied to out/lib/factor/<vocabRoot>/<vocabName>.

  2. More complex projects with several vocabularies next to each other, e.g. ./<vocabName> and ./<otherVocab>. All directories except bin, doc and lib are copied to out/lib/factor/<vocabRoot>.

  3. Even more complex projects that touch multiple vocabulary roots. Vocabularies must reside under lib/factor/<root>/<vocab> with the name-giving vocabulary being in lib/factor/<vocabRoot>/<vocabName>. All directories in lib/factor are copied to out/.

For instance, packaging the Bresenham algorithm for line interpolation looks like this, see pkgs/development/compilers/factor-lang/vocabs/bresenham for the complete file:

{ factorPackages, fetchFromGitHub }:

factorPackages.buildFactorVocab {
  pname = "bresenham";
  version = "dev";

  src = fetchFromGitHub {
    owner = "Capital-EX";
    repo = "bresenham";
    rev = "58d76b31a17f547e19597a09d02d46a742bf6808";
    hash = "sha256-cfQOlB877sofxo29ahlRHVpN3wYTUc/rFr9CJ89dsME=";
  };
}

The vocabulary goes to lib/factor/extra, extra files, like licenses etc. would go to share/ as usual and could be added to the output via a postInstall phase. In case the vocabulary binds to a shared library or calls a binary that needs to be present in the runtime environment of its users, add extraPaths and extraLibs attributes, respectively. They are then picked up by the buildFactorApplication function and added as runtime dependencies.

Building Applications

Factor applications are built using Factor’s deploy facility with the help of the buildFactorApplication function.

buildFactorApplication function

factorPackages.buildFactorApplication buildDesc

When packaging a Factor application with buildFactorApplication, its override interface should contain the factorPackages argument. For example:

{
  lib,
  fetchurl,
  factorPackages,
}:

factorPackages.buildFactorApplication (finalAttrs: {
  pname = "foo";
  version = "1.0";

  src = fetchurl {
    url = "https://some-forge.org/foo-${finalAttrs.version}.tar.gz";
  };
})

The buildFactorApplication function expects the following source structure for a package foo-1.0 and produces a /bin/foo application:

foo-1.0/
  foo/
    foo.factor
    deploy.factor
  <more files and directories>...

It provides the additional attributes vocabName and binName to cope with naming deviations. The deploy.factor file controls how the application is deployed and is documented in the Factor online documentation on the deploy facility.

Use the preInstall or postInstall hooks to copy additional files and directories to out/. The function itself only builds the application in /lib/factor/ and a wrapper in /bin/.

A more complex example shows how to specify runtime dependencies and additional Factor vocabularies at the example of the painter Factor application:

{
  lib,
  fetchFromGitHub,
  factorPackages,
  curl,
}:

factorPackages.buildFactorApplication (finalAttrs: {
  pname = "painter";
  version = "1";

  factor-lang = factorPackages.factor-minimal-gui;

  src = fetchFromGitHub {
    name = finalAttrs.vocabName;
    owner = "Capital-EX";
    repo = "painter";
    rev = "365797be8c4f82440bec0ad0a50f5a858a06c1b6";
    hash = "sha256-VdvnvKNGcFAtjWVDoxyYgRSyyyy0BEZ2MZGQ71O8nUI=";
  };

  sourceRoot = ".";

  enableUI = true;
  extraVocabs = [ factorPackages.bresenham ];

  extraPaths = with finalAttrs.factor-lang; binPackages ++ defaultBins ++ [ curl ];

})

The use of the src.name and sourceRoot attributes conveniently establish the necessary painter vocabulary directory that is needed for the deployment to work.

It requires the packager to specify the full set of binaries to be made available at runtime. This enables the standard pattern for application packages to specify all runtime dependencies explicitly without the Factor runtime interfering.

buildFactorApplication is a wrapper around stdenv.mkDerivation and takes all of its attributes. Additional attributes that are understood by buildFactorApplication:

buildDesc (Function or attribute set)

A build description similar to stdenv.mkDerivation with the following attributes:

vocabName (String; optional)

is the path to the vocabulary to be deployed relative to the source root. So, directory foo/ from the example above could be extra/deep/down/foo. This allows you to maintain Factor’s vocabulary hierarchy and distribute the same source tree as a stand-alone application and as a library in the Factor development environment via the extraVocabs attribute.

binName (String; optional)

is the name of the resulting binary in /bin/. It defaults to the last directory component in vocabName. It is also added as the meta.mainProgram attribute to facilitate nix run.

enableUI (Boolean; optional)

is false by default. Set this to true when you ship a graphical application.

extraLibs (List; optional)

adds additional libraries as runtime dependencies. Defaults to [] and is concatenated with runtimeLibs from the used factor-lang package. Use factor-minimal to minimize the closure of runtime libraries.

extraPaths (List; optional)

adds additional binaries to the runtime PATH environment variable (without adding their libraries, as well). Defaults to [] and is concatenated with defaultBins and binPackages from the used factor-lang package. Use factor-minimal to minimize the closure of runtime libraries.

deployScriptText (String; optional)

is the actual deploy Factor file that is executed to deploy the application. You can change it if you need to perform additional computation during deployment.

factor-lang (Package; optional)

overrides the Factor package to use to deploy this application, which also affects the default library bindings and programs in the runtime PATH. It defaults to factor-lang when enableUI is turned on and factor-no-gui when it is turned off. Applications that use only Factor libraries without external bindings or programs may set this to factor-minimal or factor-minimal-gui.

GNOME

Packaging GNOME applications

Programs in the GNOME universe are written in various languages but they all use GObject-based libraries like GLib, GTK or GStreamer. These libraries are often modular, relying on looking into certain directories to find their modules. However, due to Nix’s specific file system organization, this will fail without our intervention. Fortunately, the libraries usually allow overriding the directories through environment variables, either natively or thanks to a patch in nixpkgs. Wrapping the executables to ensure correct paths are available to the application constitutes a significant part of packaging a modern desktop application. In this section, we will describe various modules needed by such applications, environment variables needed to make the modules load, and finally a script that will do the work for us.

Settings

GSettings API is often used for storing settings. GSettings schemas are required, to know the type and other metadata of the stored values. GLib looks for glib-2.0/schemas/gschemas.compiled files inside the directories of XDG_DATA_DIRS.

On Linux, GSettings API is implemented using dconf backend. You will need to add dconf GIO module to GIO_EXTRA_MODULES variable, otherwise the memory backend will be used and the saved settings will not be persistent.

Last you will need the dconf database D-Bus service itself. You can enable it using programs.dconf.enable.

Some applications will also require gsettings-desktop-schemas for things like reading proxy configuration or user interface customization. This dependency is often not mentioned by upstream, you should grep for org.gnome.desktop and org.gnome.system to see if the schemas are needed.

GIO modules

GLib’s GIO library supports several extension points. Notably, they allow:

  • implementing settings backends (already mentioned)

  • adding TLS support

  • proxy settings

  • virtual file systems

The modules are typically installed to lib/gio/modules/ directory of a package and you need to add them to GIO_EXTRA_MODULES if you need any of those features.

In particular, we recommend:

  • adding dconf.lib for any software on Linux that reads GSettings (even transitively through e.g. GTK’s file manager)

  • adding glib-networking for any software that accesses network using GIO or libsoup – glib-networking contains a module that implements TLS support and loads system-wide proxy settings

To allow software to use various virtual file systems, gvfs package can be also added. But that is usually an optional feature so we typically use gvfs from the system (e.g. installed globally using NixOS module).

GdkPixbuf loaders

GTK applications typically use GdkPixbuf to load images. But gdk-pixbuf package only supports basic bitmap formats like JPEG, PNG or TIFF, requiring to use third-party loader modules for other formats. This is especially painful since GTK itself includes SVG icons, which cannot be rendered without a loader provided by librsvg.

Unlike other libraries mentioned in this section, GdkPixbuf only supports a single value in its controlling environment variable GDK_PIXBUF_MODULE_FILE. It is supposed to point to a cache file containing information about the available loaders. Each loader package will contain a lib/gdk-pixbuf-2.0/2.10.0/loaders.cache file describing the default loaders in gdk-pixbuf package plus the loader contained in the package itself. If you want to use multiple third-party loaders, you will need to create your own cache file manually. Fortunately, this is pretty rare as not many loaders exist.

gdk-pixbuf contains a setup hook that sets GDK_PIXBUF_MODULE_FILE from dependencies but as mentioned in further section, it is pretty limited. Loaders should propagate this setup hook.

Icons

When an application uses icons, an icon theme should be available in XDG_DATA_DIRS during runtime. The package for the default, icon-less hicolor-icon-theme (should be propagated by every icon theme) contains a setup hook that will pick up icon themes from buildInputs and add their datadirs to XDG_ICON_DIRS environment variable (this is Nixpkgs specific, not actually a XDG standard variable). Unfortunately, relying on that would mean every user has to download the theme included in the package expression no matter their preference. For that reason, we leave the installation of icon theme on the user. If you use one of the desktop environments, you probably already have an icon theme installed.

In the rare case you need to use icons from dependencies (e.g. when an app forces an icon theme), you can use the following to pick them up:

{
  buildInputs = [ pantheon.elementary-icon-theme ];
  preFixup = ''
    gappsWrapperArgs+=(
      # The icon theme is hardcoded.
      --prefix XDG_DATA_DIRS : "$XDG_ICON_DIRS"
    )
  '';
}

To avoid costly file system access when locating icons, GTK, as well as Qt, can rely on icon-theme.cache files from the themes’ top-level directories. These files are generated using gtk-update-icon-cache, which is expected to be run whenever an icon is added or removed to an icon theme (typically an application icon into hicolor theme) and some programs do indeed run this after icon installation. However, since packages are installed into their own prefix by Nix, this would lead to conflicts. For that reason, gtk3 provides a setup hook that will clean the file from installation. Since most applications only ship their own icon that will be loaded on start-up, it should not affect them too much. On the other hand, icon themes are much larger and more widely used so we need to cache them. Because we recommend installing icon themes globally, we will generate the cache files from all packages in a profile using a NixOS module. You can enable the cache generation using gtk.iconCache.enable option if your desktop environment does not already do that.

Packaging icon themes

Icon themes may inherit from other icon themes. The inheritance is specified using the Inherits key in the index.theme file distributed with the icon theme. According to the icon theme specification, icons not provided by the theme are looked for in its parent icon themes. Therefore the parent themes should be installed as dependencies for a more complete experience regarding the icon sets used.

The package hicolor-icon-theme provides a setup hook which makes symbolic links for the parent themes into the directory share/icons of the current theme directory in the nix store, making sure they can be found at runtime. For that to work the packages providing parent icon themes should be listed as propagated build dependencies, together with hicolor-icon-theme.

Also make sure that icon-theme.cache is installed for each theme provided by the package, and set dontDropIconThemeCache to true so that the cache file is not removed by the gtk3 setup hook.

GTK Themes

Previously, a GTK theme needed to be in XDG_DATA_DIRS. This is no longer necessary for most programs since GTK incorporated Adwaita theme. Some programs (for example, those designed for elementary HIG) might require a special theme like pantheon.elementary-gtk-theme.

GObject introspection typelibs

GObject introspection allows applications to use C libraries in other languages easily. It does this through typelib files searched in GI_TYPELIB_PATH.

Various plug-ins

If your application uses GStreamer or Grilo, you should set GST_PLUGIN_SYSTEM_PATH_1_0 and GRL_PLUGIN_PATH, respectively.

Onto wrapGApps* hooks

Given the requirements above, the package expression would become messy quickly:

{
  preFixup = ''
    for f in $(find $out/bin/ $out/libexec/ -type f -executable); do
      wrapProgram "$f" \
        --prefix GIO_EXTRA_MODULES : "${getLib dconf}/lib/gio/modules" \
        --prefix XDG_DATA_DIRS : "$out/share" \
        --prefix XDG_DATA_DIRS : "$out/share/gsettings-schemas/${name}" \
        --prefix XDG_DATA_DIRS : "${gsettings-desktop-schemas}/share/gsettings-schemas/${gsettings-desktop-schemas.name}" \
        --prefix XDG_DATA_DIRS : "${hicolor-icon-theme}/share" \
        --prefix GI_TYPELIB_PATH : "${
          lib.makeSearchPath "lib/girepository-1.0" [
            pango
            json-glib
          ]
        }"
    done
  '';
}

Fortunately, we have a family of hooks that automate this. They work in conjunction with other setup hooks that populate environment variables, and will then wrap all executables in bin and libexec directories using said variables.

  • wrapGAppsHook3 for GTK 3 apps. For convenience, it also adds dconf.lib for a GIO module implementing a GSettings backend using dconf, gtk3 for GSettings schemas, and librsvg for GdkPixbuf loader to the closure.

  • wrapGAppsHook4 for GTK 4 apps. Same as wrapGAppsHook3 but replaces gtk3 with gtk4.

  • wrapGAppsNoGuiHook for programs without a graphical interface. Same as the above but does not bring gtk3 and librsvg into the closure.

The hooks do the following:

  • wrapGApps* hook itself will add the package’s share directory to XDG_DATA_DIRS.

  • glib setup hook will populate GSETTINGS_SCHEMAS_PATH and then wrapGApps* hook will prepend it to XDG_DATA_DIRS.

  • gdk-pixbuf setup hook will populate GDK_PIXBUF_MODULE_FILE with the path to biggest loaders.cache file from the dependencies containing GdkPixbuf loaders. This works fine when there are only two packages containing loaders (gdk-pixbuf and e.g. librsvg) – it will choose the second one, reasonably expecting that it will be bigger since it describes extra loader in addition to the default ones. But when there are more than two loader packages, this logic will break. One possible solution would be constructing a custom cache file for each package containing a program like services/x11/gdk-pixbuf.nix NixOS module does. wrapGApps* hook copies the GDK_PIXBUF_MODULE_FILE environment variable into the produced wrapper.

  • One of gtk3’s setup hooks will remove icon-theme.cache files from package’s icon theme directories to avoid conflicts. Icon theme packages should prevent this with dontDropIconThemeCache = true;.

  • dconf.lib is a dependency of wrapGApps* hook, which then also adds it to the GIO_EXTRA_MODULES variable.

  • hicolor-icon-theme’s setup hook will add icon themes to XDG_ICON_DIRS.

  • gobject-introspection setup hook populates GI_TYPELIB_PATH variable with lib/girepository-1.0 directories of dependencies, which is then added to wrapper by wrapGApps* hook. It also adds share directories of dependencies to XDG_DATA_DIRS, which is intended to promote GIR files but it also pollutes the closures of packages using wrapGApps* hook.

  • Setup hooks of gst_all_1.gstreamer and grilo will populate the GST_PLUGIN_SYSTEM_PATH_1_0 and GRL_PLUGIN_PATH variables, respectively, which will then be added to the wrapper by wrapGApps* hook.

  • libglycin’s setup hook will populate XDG_DATA_DIRS with the path to the loaders.

You can also pass additional arguments to makeWrapper using gappsWrapperArgs in preFixup hook:

{
  preFixup = ''
    gappsWrapperArgs+=(
      # Thumbnailers
      --prefix XDG_DATA_DIRS : "${gdk-pixbuf}/share"
      --prefix XDG_DATA_DIRS : "${librsvg}/share"
      --prefix XDG_DATA_DIRS : "${shared-mime-info}/share"
    )
  '';
}

Updating GNOME packages

Most GNOME package offer updateScript, it is therefore possible to update to latest source tarball by running nix-shell maintainers/scripts/update.nix --argstr package nautilus or even en masse with nix-shell maintainers/scripts/update.nix --argstr path gnome. Read the package’s NEWS file to see what changed.

Frequently encountered issues

GLib-GIO-ERROR **: 06:04:50.903: No GSettings schemas are installed on the system

There are no schemas available in XDG_DATA_DIRS. Temporarily add a random package containing schemas like gsettings-desktop-schemas to buildInputs. glib and wrapGApps* setup hooks will take care of making the schemas available to application and you will see the actual missing schemas with the next error. Or you can try looking through the source code for the actual schemas used.

GLib-GIO-ERROR **: 06:04:50.903: Settings schema ‘org.gnome.foo’ is not installed

Package is missing some GSettings schemas. You can find out the package containing the schema with nix-locate org.gnome.foo.gschema.xml and let the hooks handle the wrapping as above.

When using wrapGApps* hook with special derivers or hooks you can end up with double wrapped binaries.

This is because some setup hooks like qt6.wrapQtAppsHook also wrap programs using makeWrapper. Likewise, some derivers (e.g. python.pkgs.buildPythonApplication) automatically pull in their own setup hooks that produce wrappers.

The simplest workaround is to disable the wrapGApps* hook’s automatic wrapping using dontWrapGApps = true; while passing its makeWrapper arguments to another wrapper.

In the case of a Python application it could look like:

python3.pkgs.buildPythonApplication {
  pname = "gnome-music";
  version = "3.32.2";

  nativeBuildInputs = [
    wrapGAppsHook3
    gobject-introspection
    # ...
  ];

  dontWrapGApps = true;

  # Arguments to be passed to `makeWrapper`, only used by buildPython*
  preFixup = ''
    makeWrapperArgs+=("''${gappsWrapperArgs[@]}")
  '';
}

And for a QT app like:

stdenv.mkDerivation {
  pname = "calibre";
  version = "3.47.0";

  nativeBuildInputs = [
    wrapGAppsHook3
    qt6.wrapQtAppsHook
    qmake
    # ...
  ];

  dontWrapGApps = true;

  preFixup = ''
    qtWrapperArgs+=("''${gappsWrapperArgs[@]}")
  '';
}

I am packaging a project that cannot be wrapped, like a library or GNOME Shell extension.

You can rely on applications depending on the library setting the necessary environment variables but that is often easy to miss. Instead we recommend to patch the paths in the source code whenever possible. Here are some examples:

I need to wrap a binary outside bin and libexec directories.

You can manually trigger the wrapping with wrapGApp in preFixup phase. It takes a path to a program as a first argument; the remaining arguments are passed directly to wrapProgram function.

Go

Building Go modules with buildGoModule

The function buildGoModule builds Go programs managed with Go modules. It builds Go Modules through a two phase build:

  • An intermediate fetcher derivation called goModules. This derivation will be used to fetch all the dependencies of the Go module.

  • A final derivation will use the output of the intermediate derivation to build the binaries and produce the final output.

Example for buildGoModule

The following is an example expression using buildGoModule:

{
  pet = buildGoModule (finalAttrs: {
    pname = "pet";
    version = "0.3.4";

    src = fetchFromGitHub {
      owner = "knqyf263";
      repo = "pet";
      tag = "v${finalAttrs.version}";
      hash = "sha256-Gjw1dRrgM8D3G7v6WIM2+50r4HmTXvx0Xxme2fH9TlQ=";
    };

    vendorHash = "sha256-ciBIR+a1oaYH+H1PcC8cD8ncfJczk1IiJ8iYNM+R6aA=";

    meta = {
      description = "Simple command-line snippet manager, written in Go";
      homepage = "https://github.com/knqyf263/pet";
      license = lib.licenses.mit;
      maintainers = with lib.maintainers; [ kalbasit ];
    };
  });
}

Attributes of buildGoModule

Many attributes controlling the build phase are respected by buildGoModule. Note that buildGoModule reads the following attributes also when building the vendor/ goModules fixed output derivation as well:

To control test execution of the build derivation, the following attributes are of interest:

In addition to the above attributes, and the many more variables respected also by stdenv.mkDerivation, buildGoModule respects Go-specific attributes that tweak them to behave slightly differently:

vendorHash

Hash of the output of the intermediate fetcher derivation (the dependencies of the Go modules).

vendorHash can be set to null. In that case, rather than fetching the dependencies, the dependencies already vendored in the vendor directory of the source repo will be used.

To avoid updating this field when dependencies change, run go mod vendor in your source repo and set vendorHash = null;. You can read more about vendoring in the Go documentation.

To obtain the hash, set vendorHash = lib.fakeHash; and run the build. (more details here). Another way is to use nix-prefetch to obtain the hash. The following command gets the value of vendorHash for package pet:

cd path/to/nixpkgs
nix-prefetch -E "{ sha256 }: ((import ./. { }).my-package.overrideAttrs { vendorHash = sha256; }).goModules"

vendorHash can be overridden with overrideAttrs. Override the above example like this:

{
  pet_0_4_0 = pet.overrideAttrs (
    finalAttrs: previousAttrs: {
      version = "0.4.0";
      src = fetchFromGitHub {
        inherit (previousAttrs.src) owner repo;
        tag = "v${finalAttrs.version}";
        hash = "sha256-gVTpzmXekQxGMucDKskGi+e+34nJwwsXwvQTjRO6Gdg=";
      };
      vendorHash = "sha256-dUvp7FEW09V0xMuhewPGw3TuAic/sD7xyXEYviZ2Ivs=";
    }
  );
}

proxyVendor

If true, the intermediate fetcher downloads dependencies from the Go module proxy (using go mod download) instead of vendoring them. The resulting module cache is then passed to the final derivation.

This is useful if your code depends on C code and go mod tidy does not include the needed sources to build or if any dependency has case-insensitive conflicts which will produce platform-dependent vendorHash checksums. It may also be needed if the module targets language version 1.16 or earlier, since vendoring compiles all dependencies against language version 1.16 in this case.

Defaults to false.

modPostBuild

Shell commands to run after the build of the goModules executes go mod vendor, and before calculating fixed output derivation’s vendorHash. Note that if you change this attribute, you need to update the vendorHash attribute.

modRoot

The root directory of the Go module that contains the go.mod file.

Defaults to ./, which is the root of src.

ldflags

A string list of flags to pass to the Go linker tool via the -ldflags argument of go build. Possible values can be retrieved by running go tool link --help. The most common use case for this argument is to make the resulting executable aware of its own version by injecting the value of string variable using the -X flag. For example:

{
  ldflags = [
    "-X main.Version=${version}"
    "-X main.Commit=${version}"
  ];
}

tags

A string list of Go build tags (also called build constraints) that are passed via the -tags argument of go build. These constraints control whether Go files from the source should be included in the build. For example:

{
  tags = [
    "production"
    "sqlite"
  ];
}

Tags can also be set conditionally:

{ tags = [ "production" ] ++ lib.optionals withSqlite [ "sqlite" ]; }

deleteVendor

If set to true, removes the pre-existing vendor directory. This should only be used if the dependencies included in the vendor folder are broken or incomplete.

subPackages

Specified as a string or list of strings. Limits the builder from building child packages that have not been listed. If subPackages is not specified, all child packages will be built.

Many Go projects keep the main package in a cmd directory. Following example could be used to only build the example-cli and example-server binaries:

{
  subPackages = [
    "cmd/example-cli"
    "cmd/example-server"
  ];
}

excludedPackages

Specified as a string or list of strings. Causes the builder to skip building child packages that match any of the provided values.

enableParallelBuilding

Whether builds and tests should run in parallel.

Defaults to true.

allowGoReference

Whether the build result should be allowed to contain references to the Go tool chain. This might be needed for programs that are coupled with the compiler, but shouldn’t be set without a good reason.

Defaults to false

goSum

Specifies the contents of the go.sum file and triggers rebuilds when it changes. This helps combat inconsistent dependency errors on go.sum changes.

Defaults to null

buildTestBinaries

This option allows to compile test binaries instead of the usual binaries produced by a package. Go can compile test into binaries using the go test -c command. These binaries can then be executed at a later point (outside the Nix sandbox) to run the tests. This is mostly useful for downstream consumers to run integration or end-to-end tests that won’t work in the Nix sandbox, for example because they require network access.

Versioned toolchains and builders

Beside buildGoModule, there are also versioned builders available that pin a specific Go version, like buildGo124Module for Go 1.24. Similar, versioned toolchains are available, like go_1_24 for Go 1.24. Both builder and toolchain of a certain version will be removed as soon as the Go version reaches its end of life.

As toolchain updates in nixpkgs cause mass rebuilds and must go through the staging cycle, it can take a while until a new Go minor version is available to consumers of nixpkgs. If you want quicker access to the latest minor, use go_latest toolchain and buildGoLatestModule builder. To learn more about the Go maintenance and upgrade procedure in nixpkgs, check out the Go toolchain/builder upgrade policy.

Warning

The use of go_latest and buildGoLatestModule is restricted within nixpkgs. The Go toolchain/builder upgrade policy must be followed.

Overriding goModules

Overriding <pkg>.goModules by calling goModules.overrideAttrs is unsupported. Still, it is possible to override the vendorHash (goModules’s outputHash) and the pre/post hooks for both the build and patch phases of the primary and goModules derivation.

Alternatively, the primary derivation provides an overridable passthru.overrideModAttrs function to store the attribute overlay implicitly taken by goModules.overrideAttrs. Here’s an example usage of overrideModAttrs:

{
  pet-overridden = pet.overrideAttrs (
    finalAttrs: previousAttrs: {
      passthru = previousAttrs.passthru // {
        # If the original package has an `overrideModAttrs` attribute set, you'd
        # want to extend it, and not replace it. Hence we use
        # `lib.composeExtensions`. If you are sure the `overrideModAttrs` of the
        # original package trivially does nothing, you can safely replace it
        # with your own by not using `lib.composeExtensions`.
        overrideModAttrs = lib.composeExtensions previousAttrs.passthru.overrideModAttrs (
          finalModAttrs: previousModAttrs: {
            # goModules-specific overriding goes here
            postBuild = ''
              # Here you have access to the `vendor` directory.
              substituteInPlace vendor/github.com/example/repo/file.go \
                --replace-fail "panic(err)" ""
            '';
          }
        );
      };
    }
  );
}

Controlling the Go environment

The Go build can be further tweaked by setting environment variables via the env attribute. In most cases, this isn’t needed. Possible values can be found in the Go documentation of accepted environment variables. Notice that some of these flags are set by the build helper itself and should not be set explicitly. If in doubt, grep the implementation of the build helper.

buildGoModule officially supports the following environment variables:

env.CGO_ENABLED

When set to 0, the cgo command is disabled. As a consequence, the build program can’t link against C libraries anymore, and the resulting binary is statically linked.

When building with CGO enabled, Go will likely link some packages from the Go standard library against C libraries, even when the target code does not explicitly call into C dependencies. With env.CGO_ENABLED = 0;, Go will always use the Go native implementation of these internal packages. For reference see net and os/user packages. Notice that the decision whether these packages should use native Go implementation or not can also be controlled on a per package level using build tags (tags). In case CGO is disabled, these tags have no additional effect.

When a Go program depends on C libraries, place those dependencies in buildInputs:

{
  buildInputs = [
    libvirt
    libxml2
  ];
}

env.CGO_ENABLED defaults to 1.

Skipping tests

buildGoModule runs tests by default. Failing tests can be disabled using the checkFlags parameter. This is done with the -skip or -run flags of the go test command.

For example, only a selection of tests could be run with:

{
  # -run and -skip accept regular expressions
  checkFlags = [ "-run=^Test(Simple|Fast)$" ];
}

If a larger amount of tests should be skipped, the following pattern can be used:

{
  checkFlags =
    let
      # Skip tests that require network access
      skippedTests = [
        "TestNetwork"
        "TestDatabase/with_mysql" # exclude only the subtest
        "TestIntegration"
      ];
    in
    [ "-skip=^${builtins.concatStringsSep "$|^" skippedTests}$" ];
}

To disable tests altogether, set doCheck = false;.

Migrating from buildGoPackage to buildGoModule

Warning

buildGoPackage was removed for the 25.05 release. It was used to build legacy Go programs that do not support Go modules.

Go modules, released 6y ago, are now widely adopted in the ecosystem. Most upstream projects are using Go modules, and the tooling previously used for dependency management in Go is mostly deprecated, archived or at least unmaintained at this point.

In case a project doesn’t have external dependencies or dependencies are vendored in a way understood by go mod init, migration can be done with a few changes in the package.

  • Switch the builder from buildGoPackage to buildGoModule

  • Remove goPackagePath and other attributes specific to buildGoPackage

  • Set vendorHash = null;

  • Run go mod init <module name> in postPatch

In case the package has external dependencies that aren’t vendored or the build setup is more complex the upstream source might need to be patched. Examples for the migration can be found in the issue tracking migration within nixpkgs.

Gradle

Gradle is a popular build tool for Java/Kotlin. Gradle itself doesn’t currently provide tools to make dependency resolution reproducible, so nixpkgs has a proxy designed for intercepting Gradle web requests to record dependencies so they can be restored in a reproducible fashion.

Building a Gradle package

Here’s how a typical derivation will look:

stdenv.mkDerivation (finalAttrs: {
  pname = "pdftk";
  version = "3.3.3";

  src = fetchFromGitLab {
    owner = "pdftk-java";
    repo = "pdftk";
    tag = "v${finalAttrs.version}";
    hash = "sha256-ciKotTHSEcITfQYKFZ6sY2LZnXGChBJy0+eno8B3YHY=";
  };

  nativeBuildInputs = [
    gradle
    makeWrapper
  ];

  # if the package has dependencies, mitmCache must be set
  mitmCache = gradle.fetchDeps {
    inherit (finalAttrs) pname;
    data = ./deps.json;
  };

  # this is required for using mitm-cache on Darwin
  __darwinAllowLocalNetworking = true;

  gradleFlags = [ "-Dfile.encoding=utf-8" ];

  # defaults to "assemble"
  gradleBuildTask = "shadowJar";

  # will run the gradleCheckTask (defaults to "test")
  doCheck = true;

  installPhase = ''
    mkdir -p $out/{bin,share/pdftk}
    cp build/libs/pdftk-all.jar $out/share/pdftk

    makeWrapper ${lib.getExe jre} $out/bin/pdftk \
      --add-flags "-jar $out/share/pdftk/pdftk-all.jar"

    cp ${finalAttrs.src}/pdftk.1 $out/share/man/man1
  '';

  meta.sourceProvenance = with lib.sourceTypes; [
    fromSource
    binaryBytecode # mitm cache
  ];
})

To update (or initialize) dependencies, run the update script via something like $(nix-build -A <pname>.mitmCache.updateScript) (nix-build builds the updateScript, $(...) runs the script at the path printed by nix-build).

If your package can’t be evaluated using a simple pkgs.<pname> expression (for example, if your package isn’t located in nixpkgs, or if you want to override some of its attributes), you will usually have to pass pkg instead of pname to gradle.fetchDeps. There are two ways of doing so.

The first is to add the derivation arguments required for getting the package. Using the pdftk example above:

{
  lib,
  stdenv,
  gradle,
  # ...
  pdftk,
}:

stdenv.mkDerivation (finalAttrs: {
  # ...
  mitmCache = gradle.fetchDeps {
    pkg = pdftk;
    data = ./deps.json;
  };
})

This allows you to override any arguments of the pkg used for the update script (for example, pkg = pdftk.override { enableSomeFlag = true };).

The second is to use finalAttrs.finalPackage like this:

stdenv.mkDerivation (finalAttrs: {
  # ...
  mitmCache = gradle.fetchDeps {
    pkg = finalAttrs.finalPackage;
    data = ./deps.json;
  };
})

The limitation of this method is that you cannot override the pkg derivations’s arguments.

In the former case, the update script will stay the same even if the derivation is called with different arguments. In the latter case, the update script will change depending on the derivation arguments. It’s up to you to decide which one would work best for your derivation.

Update Script

The update script does the following:

  • Build the derivation’s source via pkgs.srcOnly

  • Enter a nix-shell for the derivation in a bwrap sandbox (the sandbox is only used on Linux)

  • Set the IN_GRADLE_UPDATE_DEPS environment variable to 1

  • Run the derivation’s unpackPhase, patchPhase, configurePhase

  • Run the derivation’s gradleUpdateScript (the Gradle setup hook sets a default value for it, which runs preBuild, preGradleUpdate hooks, fetches the dependencies using gradleUpdateTask, and finally runs the postGradleUpdate hook)

  • Finally, store all of the fetched files’ hashes in the lockfile. They may be .jar/.pom files from Maven repositories, or they may be files otherwise used for building the package.

fetchDeps takes the following arguments:

  • attrPath - the path to the package in nixpkgs (for example, "javaPackages.openjfx25"). Used for update script metadata.

  • pname - an alias for attrPath for convenience. This is what you will generally use instead of pkg or attrPath.

  • pkg - the package to be used for fetching the dependencies. Defaults to getAttrFromPath (splitString "." attrPath) pkgs.

  • bwrapFlags - allows you to override bwrap flags (only relevant for downstream, non-nixpkgs projects)

  • data - path to the dependencies lockfile (can be relative to the package, can be absolute). In nixpkgs, it’s discouraged to have the lockfiles be named anything other than deps.json. Consider creating subdirectories if your package requires multiple deps.json files.

Environment

The Gradle setup hook accepts the following environment variables:

  • mitmCache - the MITM proxy cache imported using gradle.fetchDeps

  • gradleFlags - command-line flags to be used for every Gradle invocation (this simply registers a function that uses the necessary flags).

    • You can’t use gradleFlags for flags that contain spaces, in that case you must add gradleFlagsArray+=("-flag with spaces") to the derivation’s bash code instead.

    • If you want to build the package using a specific Java version, you can pass "-Dorg.gradle.java.home=${jdk}" as one of the flags.

  • gradleBuildTask - the Gradle task (or tasks) to be used for building the package. Defaults to assemble.

  • gradleCheckTask - the Gradle task (or tasks) to be used for checking the package if doCheck is set to true. Defaults to test.

  • gradleUpdateTask - the Gradle task (or tasks) to be used for fetching all of the package’s dependencies in mitmCache.updateScript. Defaults to nixDownloadDeps.

  • gradleUpdateScript - the code to run for fetching all of the package’s dependencies in mitmCache.updateScript. Defaults to running the preBuild and preGradleUpdate hooks, running the gradleUpdateTask, and finally running the postGradleUpdate hook.

  • gradleInitScript - path to the --init-script to pass to Gradle. By default, a simple init script that enables reproducible archive creation is used.

    • Note that reproducible archives might break some builds. One example of an error caused by it is Could not create task ':jar'. Replacing an existing task that may have already been used by other plugins is not supported. If you get such an error, the easiest “fix” is disabling reproducible archives altogether by setting gradleInitScript to something like writeText "empty-init-script.gradle" ""

  • enableParallelBuilding / enableParallelChecking / enableParallelUpdating - pass --parallel to Gradle in the build/check phase or in the update script. Defaults to true. If the build fails for mysterious reasons, consider setting this to false.

  • dontUseGradleConfigure / dontUseGradleBuild / dontUseGradleCheck - force disable the Gradle setup hook for certain phases.

    • Note that if you disable the configure hook, you may face issues such as Failed to load native library 'libnative-platform.so', because the configure hook is responsible for initializing Gradle.

Hare

Building Hare programs with hareHook

The hareHook package sets up the environment for building Hare programs by doing the following:

  1. Setting the HARECACHE, HAREPATH and NIX_HAREFLAGS environment variables;

  2. Propagating harec, qbe and two wrapper scripts for the hare binary.

It is not a function as is the case for some other languages — e. g., Go or Rust —, but a package to be added to nativeBuildInputs.

Attributes of hareHook

The following attributes are accepted by hareHook:

  1. hareBuildType: Either release (default) or debug. It controls if the -R flag is added to NIX_HAREFLAGS.

Example for hareHook

{
  hareHook,
  lib,
  stdenv,
}:
stdenv.mkDerivation {
  pname = "<name>";
  version = "<version>";
  src = "<src>";

  nativeBuildInputs = [ hareHook ];

  meta = {
    description = "<description>";
    inherit (hareHook) badPlatforms platforms;
  };
}

Cross Compilation

hareHook should handle cross compilation out of the box. This is the main purpose of NIX_HAREFLAGS: In it, the -a flag is passed with the architecture of the hostPlatform.

However, manual intervention may be needed when a binary compiled by the build process must be run for the build to complete — e. g., when using Hare’s hare module for code generation.

In those cases, hareHook provides the hare-native script, which is a wrapper around the hare binary for using the native (buildPlatform) toolchain.

Haskell

The Haskell infrastructure in Nixpkgs has two main purposes: The primary purpose is to provide a Haskell compiler and build tools as well as infrastructure for packaging Haskell-based packages.

The secondary purpose is to provide support for Haskell development environments including prebuilt Haskell libraries. However, in this area sacrifices have been made due to self-imposed restrictions in Nixpkgs, to lessen the maintenance effort and to improve performance. (More details in the subsection Limitations.)

Available packages

The compiler and most build tools are exposed at the top level:

  • ghc is the default version of GHC

  • Language specific tools: cabal-install, stack, hpack, …

Many “normal” user-facing packages written in Haskell, like niv or cachix, are also exposed at the top level, and there is nothing Haskell specific to installing and using them.

All of these packages are originally defined in the haskellPackages package set. The same packages are re-exposed with a reduced dependency closure for convenience (see justStaticExecutables or separateBinOutput below).

Note

See Languages and frameworks for techniques to explore package sets.

The haskellPackages set includes at least one version of every package from Hackage as well as some manually injected packages.

The attribute names in haskellPackages always correspond with their name on Hackage. Since Hackage allows names that are not valid Nix without escaping, you need to take care when handling attribute names like 3dmodels.

For packages that are part of Stackage (a curated set of known to be compatible packages), we use the version prescribed by a Stackage snapshot (usually the current LTS one) as the default version. For all other packages we use the latest version from Hackage (the repository of basically all open source Haskell packages). See below for a few more details on this.

Roughly half of the 16K packages contained in haskellPackages don’t actually build and are marked as broken semi-automatically. Most of those packages are deprecated or unmaintained, but sometimes packages that should build, do not build. Very often fixing them is not a lot of work.

haskellPackages is built with our default compiler, but we also provide other releases of GHC and package sets built with them. Available compilers are collected under haskell.compiler.

Each of those compiler versions has a corresponding attribute set packages built with it. However, the non-standard package sets are not tested regularly and, as a result, contain fewer working packages. The corresponding package set for GHC 9.4.8 is haskell.packages.ghc948. In fact, haskellPackages (at the time of writing) is just an alias for haskell.packages.ghc9103.

Every package set also re-exposes the GHC used to build its packages as haskell.packages.*.ghc.

Available package versions

We aim for a “blessed” package set which only contains one version of each package, like Stackage, which is a curated set of known to be compatible packages. We use the version information from Stackage snapshots and extend it with more packages. Normally in Nixpkgs the number of building Haskell packages is roughly two to three times the size of Stackage. For choosing the version to use for a certain package we use the following rules:

  1. By default, for haskellPackages.foo is the newest version of the package foo found on Hackage, which is the central registry of all open source Haskell packages. Nixpkgs contains a reference to a pinned Hackage snapshot, thus we use the state of Hackage as of the last time we updated this pin.

  2. If the Stackage snapshot that we use (usually the newest LTS snapshot) contains a package, we use instead the version in the Stackage snapshot as default version for that package.

  3. For some packages, which are not on Stackage, we have if necessary manual overrides to set the default version to a version older than the newest on Hackage.

  4. For all packages, for which the newest Hackage version is not the default version, there will also be a haskellPackages.foo_x_y_z package with the newest version. The x_y_z part encodes the version with dots replaced by underscores. When the newest version changes by a new release to Hackage the old package will disappear under that name and be replaced by a newer one under the name with the new version. The package name including the version will also disappear when the default version e.g. from Stackage catches up with the newest version from Hackage. E.g. if haskellPackages.foo gets updated from 1.0.0 to 1.1.0 the package haskellPackages.foo_1_1_0 becomes obsolete and gets dropped.

  5. For some packages, we also manually add other haskellPackages.foo_x_y_z versions, if they are required for a certain build.

Relying on haskellPackages.foo_x_y_z attributes in derivations outside nixpkgs is discouraged because they may change or disappear with every package set update.

All haskell.packages.* package sets use the same package descriptions and the same sets of versions by default. There are however GHC version specific override .nix files to loosen this a bit.

Dependency resolution

Normally when you build Haskell packages with cabal-install, cabal-install does dependency resolution. It will look at all Haskell package versions known on Hackage and try to pick for every (transitive) dependency of your build exactly one version. Those versions need to satisfy all the version constraints given in the .cabal file of your package and all its dependencies.

The Haskell builder in nixpkgs does no such thing. It will take as input packages with names of the desired dependencies and just check whether they fulfill the version bounds and fail if they don’t (by default, see jailbreak to circumvent this).

The haskellPackages.callPackage function does the package resolution. It will, e.g., use haskellPackages.aesonwhich has the d