JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
682ae7e893
nixpkgs/pkgs/top-level/impure.nix

69 lines
2.5 KiB
Nix
Raw Normal View History

Separate fix-point from config importing hacks and other impurities
2016-04-26 18:53:31 +01:00
/* Impure default args for `pkgs/top-level/default.nix`. See that file
for the meaning of each argument. */
$NIXPKGS_OVERLAYS -> <nixpkgs-overlays> The Nix search path is the established mechanism for specifying the location of Nix expressions, so let's use it instead of adding another environment variable.
2017-02-01 14:56:02 +00:00
with builtins;
let
homeDir = builtins.getEnv "HOME";
# Return ‘x’ if it evaluates, or ‘def’ if it throws an exception.
try = x: def: let res = tryEval x; in if res.success then res.value else def;
in
top-level: Allow nixpkgs to take localSystem directly This is instead of both system and platform, which is kind of ugly.
2017-02-08 21:43:52 +00:00
{ # We combine legacy `system` and `platform` into `localSystem`, if
# `localSystem` was not passed. Strictly speaking, this is pure desugar, but
# it is most convient to do so before the impure `localSystem.system` default,
# so we do it now.
localSystem ? builtins.intersectAttrs { system = null; platform = null; } args
Separate fix-point from config importing hacks and other impurities
2016-04-26 18:53:31 +01:00
top-level: Hack around Nix's --arg logic not handling unnamed params
2017-02-09 16:21:07 +00:00
, # These are needed only because nix's `--arg` command-line logic doesn't work
# with unnamed parameters allowed by ...
system ? localSystem.system
, platform ? localSystem.platform
Separate fix-point from config importing hacks and other impurities
2016-04-26 18:53:31 +01:00
, # Fallback: The contents of the configuration file found at $NIXPKGS_CONFIG or
~/.nixpkgs -> ~/.config/nixpkgs The former is still respected as a fallback for config.nix for backwards compatibility (but not for overlays because they're a new feature).
2017-02-01 15:03:42 +00:00
# $HOME/.config/nixpkgs/config.nix.
Separate fix-point from config importing hacks and other impurities
2016-04-26 18:53:31 +01:00
config ? let
configFile = getEnv "NIXPKGS_CONFIG";
~/.nixpkgs -> ~/.config/nixpkgs The former is still respected as a fallback for config.nix for backwards compatibility (but not for overlays because they're a new feature).
2017-02-01 15:03:42 +00:00
configFile2 = homeDir + "/.config/nixpkgs/config.nix";
configFile3 = homeDir + "/.nixpkgs/config.nix"; # obsolete
Separate fix-point from config importing hacks and other impurities
2016-04-26 18:53:31 +01:00
in
if configFile != "" && pathExists configFile then import configFile
else if homeDir != "" && pathExists configFile2 then import configFile2
~/.nixpkgs -> ~/.config/nixpkgs The former is still respected as a fallback for config.nix for backwards compatibility (but not for overlays because they're a new feature).
2017-02-01 15:03:42 +00:00
else if homeDir != "" && pathExists configFile3 then import configFile3
Separate fix-point from config importing hacks and other impurities
2016-04-26 18:53:31 +01:00
else {}
Add overlays mechanism to Nixpkgs. This patch add a new argument to Nixpkgs default expression named "overlays". By default, the value of the argument is either taken from the environment variable `NIXPKGS_OVERLAYS`, or from the directory `~/.nixpkgs/overlays/`. If the environment variable does not name a valid directory then this mechanism would fallback on the home directory. If the home directory does not exists it will fallback on an empty list of overlays. The overlays directory should contain the list of extra Nixpkgs stages which would be used to extend the content of Nixpkgs, with additional set of packages. The overlays, i-e directory, files, symbolic links are used in alphabetical order. The simplest overlay which extends Nixpkgs with nothing looks like: ```nix self: super: { } ``` More refined overlays can use `super` as the basis for building new packages, and `self` as a way to query the final result of the fix-point. An example of overlay which extends Nixpkgs with a small set of packages can be found at: https://github.com/nbp/nixpkgs-mozilla/blob/nixpkgs-overlay/moz-overlay.nix To use this file, checkout the repository and add a symbolic link to the `moz-overlay.nix` file in `~/.nixpkgs/overlays` directory.
2016-12-17 18:05:21 +00:00
, # Overlays are used to extend Nixpkgs collection with additional
# collections of packages. These collection of packages are part of the
# fix-point made by Nixpkgs.
overlays ? let
$NIXPKGS_OVERLAYS -> <nixpkgs-overlays> The Nix search path is the established mechanism for specifying the location of Nix expressions, so let's use it instead of adding another environment variable.
2017-02-01 14:56:02 +00:00
dirPath = try (if pathExists <nixpkgs-overlays> then <nixpkgs-overlays> else "") "";
~/.nixpkgs -> ~/.config/nixpkgs The former is still respected as a fallback for config.nix for backwards compatibility (but not for overlays because they're a new feature).
2017-02-01 15:03:42 +00:00
dirHome = homeDir + "/.config/nixpkgs/overlays";
Add overlays mechanism to Nixpkgs. This patch add a new argument to Nixpkgs default expression named "overlays". By default, the value of the argument is either taken from the environment variable `NIXPKGS_OVERLAYS`, or from the directory `~/.nixpkgs/overlays/`. If the environment variable does not name a valid directory then this mechanism would fallback on the home directory. If the home directory does not exists it will fallback on an empty list of overlays. The overlays directory should contain the list of extra Nixpkgs stages which would be used to extend the content of Nixpkgs, with additional set of packages. The overlays, i-e directory, files, symbolic links are used in alphabetical order. The simplest overlay which extends Nixpkgs with nothing looks like: ```nix self: super: { } ``` More refined overlays can use `super` as the basis for building new packages, and `self` as a way to query the final result of the fix-point. An example of overlay which extends Nixpkgs with a small set of packages can be found at: https://github.com/nbp/nixpkgs-mozilla/blob/nixpkgs-overlay/moz-overlay.nix To use this file, checkout the repository and add a symbolic link to the `moz-overlay.nix` file in `~/.nixpkgs/overlays` directory.
2016-12-17 18:05:21 +00:00
dirCheck = dir: dir != "" && pathExists (dir + "/.");
overlays = dir:
let content = readDir dir; in
$NIXPKGS_OVERLAYS -> <nixpkgs-overlays> The Nix search path is the established mechanism for specifying the location of Nix expressions, so let's use it instead of adding another environment variable.
2017-02-01 14:56:02 +00:00
map (n: import (dir + ("/" + n)))
Only read overlays ending in .nix For example, this prevents Nix from barfing on editor backup files in ~/.nixpkgs/overlays.
2017-01-31 14:20:28 +00:00
(builtins.filter (n: builtins.match ".*\.nix" n != null)
Remove unnecessary "sort" call attrNames already returns names in sorted order.
2017-02-01 19:25:58 +00:00
(attrNames content));
Add overlays mechanism to Nixpkgs. This patch add a new argument to Nixpkgs default expression named "overlays". By default, the value of the argument is either taken from the environment variable `NIXPKGS_OVERLAYS`, or from the directory `~/.nixpkgs/overlays/`. If the environment variable does not name a valid directory then this mechanism would fallback on the home directory. If the home directory does not exists it will fallback on an empty list of overlays. The overlays directory should contain the list of extra Nixpkgs stages which would be used to extend the content of Nixpkgs, with additional set of packages. The overlays, i-e directory, files, symbolic links are used in alphabetical order. The simplest overlay which extends Nixpkgs with nothing looks like: ```nix self: super: { } ``` More refined overlays can use `super` as the basis for building new packages, and `self` as a way to query the final result of the fix-point. An example of overlay which extends Nixpkgs with a small set of packages can be found at: https://github.com/nbp/nixpkgs-mozilla/blob/nixpkgs-overlay/moz-overlay.nix To use this file, checkout the repository and add a symbolic link to the `moz-overlay.nix` file in `~/.nixpkgs/overlays` directory.
2016-12-17 18:05:21 +00:00
in
$NIXPKGS_OVERLAYS -> <nixpkgs-overlays> The Nix search path is the established mechanism for specifying the location of Nix expressions, so let's use it instead of adding another environment variable.
2017-02-01 14:56:02 +00:00
if dirPath != "" then
overlays dirPath
Add overlays mechanism to Nixpkgs. This patch add a new argument to Nixpkgs default expression named "overlays". By default, the value of the argument is either taken from the environment variable `NIXPKGS_OVERLAYS`, or from the directory `~/.nixpkgs/overlays/`. If the environment variable does not name a valid directory then this mechanism would fallback on the home directory. If the home directory does not exists it will fallback on an empty list of overlays. The overlays directory should contain the list of extra Nixpkgs stages which would be used to extend the content of Nixpkgs, with additional set of packages. The overlays, i-e directory, files, symbolic links are used in alphabetical order. The simplest overlay which extends Nixpkgs with nothing looks like: ```nix self: super: { } ``` More refined overlays can use `super` as the basis for building new packages, and `self` as a way to query the final result of the fix-point. An example of overlay which extends Nixpkgs with a small set of packages can be found at: https://github.com/nbp/nixpkgs-mozilla/blob/nixpkgs-overlay/moz-overlay.nix To use this file, checkout the repository and add a symbolic link to the `moz-overlay.nix` file in `~/.nixpkgs/overlays` directory.
2016-12-17 18:05:21 +00:00
else if dirCheck dirHome then overlays dirHome
else []
Separate fix-point from config importing hacks and other impurities
2016-04-26 18:53:31 +01:00
, ...
} @ args:
top-level: Allow nixpkgs to take localSystem directly This is instead of both system and platform, which is kind of ugly.
2017-02-08 21:43:52 +00:00
# If `localSystem` was explicitly passed, legacy `system` and `platform` should
# not be passed.
assert args ? localSystem -> !(args ? system || args ? platform);
import ./. (builtins.removeAttrs args [ "system" "platform" ] // {
inherit config overlays;
# Fallback: Assume we are building packages on the current (build, in GNU
# Autotools parlance) system.
localSystem = { system = builtins.currentSystem; } // localSystem;
})
Reference in New Issue Copy Permalink