Jeff Huffman

The first few paragraphs are the hardest to get right, but also the most important. I'm sure it'll take some iterating. Is it enough to just make it: > This...

I may be misunderstanding here, but from what I can see, the bootloader backend's responsibility is totally unspecified when it comes to initrd secrets. Is this proposal assuming that the...

Much clearer regarding the initrd secrets. One thing could maybe do with a bit more clarification, though: Are the key strings of the initrd secrets hashmap meaningful to the bootloader...

For anyone looking to work around this problem, this may be helpful: https://github.com/tejing1/nixos-config/commit/4767d88783623c32580889b10e4eead2d4782e9d

For a nixos config, my original example is closer to what you want. Assuming you pass `inputs` through `specialArgs`, putting this in a file and adding it to `imports` should...

Same problem for the new `rules` option as well, which is intended to supercede many of the previous options. Guess I'm going to switch to `xdg.configFile` for this one for...

Hmm, you should be able to use the new options and still use the module, actually, since the `xdg.configFile..text` option is mergeable, so you can use it like an `extraConfig`...

Could nix by default use `path:.` instead of `git+file:.` when `flake.nix` is untracked and/or gitignored? It would at least streamline the local-only `flake.nix` usecase.

> Any solution to this pattern of usage!? If you refer to `path:.#output` instead of `.#output`, I believe it should consider the directory itself, without regard to git. That has...

Same thing occurs with `git+file://` vs bare path. And when building `github:nixos/nixpkgs/nixos-unstable#hello` inside the nix store. I'm starting to think it's just anytime the url contains `:`.