-
To provide Nix repositories with an easy and standard way to reference other Nix repositories.
-
To allow such references to be queried and updated automatically.
-
To provide a replacement for
nix-channel,NIX_PATHand Hydra
| struct FSAccessor { | |
| virtual Stat stat(const Path & path) = 0; | |
| virtual StringSet readDirectory(const Path & path) = 0; | |
| virtual std::string readFile(const Path & path) = 0; | |
| virtual std::string readLink(const Path & path) = 0; | |
| }; | |
| // Accessor to the actual filesystem. | |
| struct RealFSAccessor { ... }; |
| with import <nixpkgs> { system = "i686-linux"; }; | |
| rec { | |
| mesBoot0 = import <nix/fetchurl.nix> { | |
| url = http://alpha.gnu.org/gnu/guix/bootstrap/i686-linux/20181020/mes-minimal-stripped-0.18-0.08f04f5-i686-linux.tar.xz; | |
| sha256 = "0qwpby91hp6afmg5ibdrrk3fw85zxdazfk7rhrdsihsfzqwmfhfx"; | |
| }; | |
| mesccToolsBoot = import <nix/fetchurl.nix> { |
This document contains some ideas for additions to the Nix language.
The Nix package manager, Nixpkgs and NixOS currently have several problems:
- Poor discoverability of package options. Package functions have
function arguments like
enableFoo, but there is no way for the Nix UI to discover them, let alone to provide programmatic ways to
-
nix-channeland~/.nix-defexprare gone. We'll use$NIX_PATH(or user environment specific overrides configured vianix set-path) to look up packages. Since$NIX_PATHsupports URLs nowadays, this removes the need for channels: you can just set$NIX_PATHto e.g.https://nixos.org/channels/nixos-15.09/nixexprs.tar.xzand stay up to date automatically. -
By default, packages are selected by attribute name, rather than the
nameattribute. Thusnix install hellois basically equivalent tonix-env -iA hello. The attribute name is recorded in the user environment manifest and used in upgrades. Thus (at least by default)hellowon't be upgraded tohelloVariant.@vcunat suggested making this an arbitrary Nix expression rather than an attrpath, e.g.
firefox.override { enableFoo = true; }. However, such an expression would not have a key in the user environment, unlike an attrpath. Better to require an explicit flag for this.
TBD: How to deal with search path clashes.