Hello, @goldstein. Now that I've been adding support for different fetch/pinning tools, like yours unflake, npins, nixlock at flake-file, I also created a template for each of them. These...
another (newly born) lock project appeared in my radar: https://github.com/anialic/nixy-lock
unflake run, unflake shell etc
But having shared outputs schema (a nix-module with typed options for nixosConfigurations, packages, shells, checks, etc that can be extended so users provide their own "output field"...
unflake run, unflake shell etc
Hm, now I'm wondering if it is even worth for "default non depending on ./unflake.nix`, because each project will only have one way to load inputs, it needs not to be generic, right ? just use...
unflake run, unflake shell etc
I'm sorry if my explanation was not really clear, I guess the idea is itself shaping in my head, so apologies for just dumping a non-organized thought here.
unflake run, unflake shell etc
Hey @goldstein, I'd like your valuable input on this, and I'm writing here because it might be related to having an unflake CLI.
+1 on this.
@goldstein, just wanted to say that I've been learning a lot about from your work here. I like your detailed comments on issues, they provide much light (all unknown to me) of things nix is doing...
@goldstein done, used the same --eval approach as discover_input_names does.
Shall we remove withInputs ? I keep it for now since maybe other people is already using it.