builtin:buildenv and builtin:unpack-channel builders
Both of these are in active use inside Lix:
- buildenv:
dad17a54f7/lix/legacy/user-env.cc (L99) - unpack-channel:…
yeah, it's just like. nix-store and nix-env flags that use it, iirc. I'd be tempted to just remove the distinction; nix is already expensive (in request count) on substituters without it..
This should be conditional on devenv taking nix as argument - it's possible people are still on older nixpkgs versions.
post-build-hook blocks parallel builds
It's a regression, but not one I'm very sure of how to fix sensibly. Some time after 2.3, Nix closed the soundness hole of allowing references for FOD store paths. This makes sense, as they aren't…
This should be mostly fixed now? Dropping the thread will just detach it; and joining it now behaves as intended.
lix foo should invoke lix-foo
Some question: How do we want to handle e.g. --store or other nix-global arguments? Do we pass these as specific environment variables, I guess?
channel: "file" syntax
yeah; I'm not too fussed since it's nixpkgs-specific; it might be a good first example for #342 (aka a nix-shell but nixpkgs-specific, including easy channel selection) even.
channel: "file" syntax
I actually use this personally; mostly in the form of NIX_PATH=nixpkgs=channel:nixos-unstable nix-shell -p foo for fetching something from nixos-unstable quickly. I don't strongly mind it…