lix/tests/lang/eval-okay-search-path.nix

with import ./lib.nix;
with builtins;

assert pathExists <nix/buildenv.nix>;

assert length nixPath == 3;
assert length (filter (x: x.prefix == "nix") nixPath) == 1;
assert length (filter (x: baseNameOf x.path == "dir4") nixPath) == 1;

import <a.nix> + import <b.nix> + import <c.nix> + import <dir5/c.nix>
Add constant ‘nixPath’ It contains the Nix expression search path as a list of { prefix, path } sets, e.g. [ { path = "/nix/var/nix/profiles/per-user/root/channels/nixos"; prefix = ""; } { path = "/etc/nixos/configuration.nix"; prefix = "nixos-config"; } { path = "/home/eelco/Dev/nix/inst/share/nix/corepkgs"; prefix = "nix"; } ] 2014-05-26 12:55:47 +00:00			`with import ./lib.nix;`
			`with builtins;`

			`assert pathExists <nix/buildenv.nix>;`

			`assert length nixPath == 3;`
			`assert length (filter (x: x.prefix == "nix") nixPath) == 1;`
			`assert length (filter (x: baseNameOf x.path == "dir4") nixPath) == 1;`
* Add a Nix expression search path feature. Paths between angle brackets, e.g. import <nixpkgs/pkgs/lib> are resolved by looking them up relative to the elements listed in the search path. This allows us to get rid of hacks like import "${builtins.getEnv "NIXPKGS_ALL"}/pkgs/lib" The search path can be specified through the ‘-I’ command-line flag and through the colon-separated ‘NIX_PATH’ environment variable, e.g., $ nix-build -I /etc/nixos ... If a file is not found in the search path, an error message is lazily thrown. 2011-08-06 16:05:24 +00:00
* Add the Nix corepkgs to the end of the search path. This makes it possible for other Nix expressions to use corepkgs (mostly useful for the buildenv function). 2011-08-06 18:23:38 +00:00			`import <a.nix> + import <b.nix> + import <c.nix> + import <dir5/c.nix>`