nix-daemon.nix: Add option nix.registry #84125
Conversation
This allows you to specify the system-wide flake registry. One use is
to pin 'nixpkgs' to the Nixpkgs version used to build the system:
nix.registry.nixpkgs.flake = nixpkgs;
where 'nixpkgs' is a flake input. This ensures that commands like
$ nix run nixpkgs#hello
pull in a minimum of additional store paths.
You can also use this to redirect flakes, e.g.
nix.registry.nixpkgs.to = {
type = "github";
owner = "my-org";
repo = "my-nixpkgs";
};
ofborg
bot
added
8.has: module (update)
10.rebuild-darwin: 0
10.rebuild-linux: 1-10
labels
| to = mkOption { | ||
| type = inputAttrs; | ||
| example = { type = "github"; owner = "my-org"; repo = "my-nixpkgs"; }; | ||
| description = "The flake reference to which <option>from></option> is to be rewritten."; |
| description = "The flake reference to which <option>from></option> is to be rewritten."; | ||
| }; | ||
| flake = mkOption { | ||
| type = types.unspecified; |
| default = null; | ||
| example = literalExample "nixpkgs"; | ||
| description = '' | ||
| The flake input to which <option>from></option> is to be rewritten. |
There was a problem hiding this comment.
It's not clear to me what "a flake input" means here. Input seems to be a role, rather than an intrinsic description of what it is that you need here. I guess you could equally say "a flake output attrset", because that's what defines an invoked flake. It'd also be helpful to know by which means this configuration is stored.
What happens when you use this option in a flake where you use inputs.<input>.follows? I don't think that important context preserved, is it?
| } // lib.filterAttrs | ||
| (n: v: n == "lastModified" || n == "rev" || n == "revCount" || n == "narHash") | ||
| config.flake); |
There was a problem hiding this comment.
This is // { inherit (config.flake) .....; }
| )); | ||
| default = {}; | ||
| description = '' | ||
| A system-wide flake registry. |
There was a problem hiding this comment.
What does it do? Maybe reference the Nix manual?
|
I'm using NixOS 21.11 and Nix 2.4. I'd like to globally pin the nixpkgs flake to the same version as my system. {
# ...
nix.registry.nixpkgs.flake = pkgs;
}But this causes an error: Is the documentation out of date or am I doing something wrong? |
|
Ok I might have made a bit of progress. I tried this and now at least the build works: {
# ...
nix.registry.nixpkgs.flake.outPath = toString <nixpkgs>;
}But when using $ nix develop
warning: Git tree '/home/matt/projectxyz' is dirty
error: access to path '/nix/store/nv5hy4qdqv1cqlhqg8wv3lpvjqn6jpdx-nixos-21.11.335443.e84444b14cc/nixos/flake.nix' is forbidden in restricted mode |
|
Here is what I do: where |
|
@edolstra Thank you for the response and thank you for bringing the awesomeness that is Nix/NixOS to the world. I read your blog post, that is where I saw that it was possible to configure the registry and when it didn't work I tracked it down in the code to this MR. I don't currently have my NixOS configuration set up as a flake, so I think I would have to switch to a flake-based system config to do this. This was my plan anyways, but I was just starting to experiment with flakes to replace Regarding pure-evaluation: I see that |
This allows you to specify the system-wide flake registry. One use is to pin
nixpkgsto the Nixpkgs version used to build the system:where
nixpkgsis a flake input. This ensures that commands likepull in a minimum of additional store paths.
You can also use this to redirect flakes, e.g.
Motivation for this change
Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)nix path-info -Sbefore and after)