<bqv>
infinisil: yeah, but i would have assumed that'd be separate-ish to the versioning of the flake, but come to think of it that might be overcomplicating things
<infinisil>
Hm, or maybe we don't put the full repo at the target machine
<infinisil>
But rather only the commit sha1 of the current state
<infinisil>
Eh maybe not
<infinisil>
The idea being you can rebuild locally on a machine if necessary
<infinisil>
Eh, it's an idea-in-progress, but I feel like it might work well with flakes, because they really ensure that the git repo describes the whole system
<bqv>
sorry, people wont leave me the heck alone
<bqv>
yeah, i like that idea
<bqv>
have a nixus.nix next to your flake.nix, or something?
<bqv>
or have it as part of the flake as a defined attr?
<infinisil>
Well in the nixus repo it would just be a flake.nix I guess, which defines the function to build the deployment
<infinisil>
But in your own repo you'd depend on the nixus flake and use that function in your flake.nix probably
<bqv>
makes sense
<infinisil>
Oh and you'd probably depend on all the nixpkgs versions you wanted for your systems too as a flake input
<infinisil>
And would pass that to the function somehow (probably via the nixpkgs option in nixus)
<bqv>
right, that was the big issue with nixus, it integrates tightly to the nixosSystem so it needs a nixpkgs and to be imported as a module(?)
<infinisil>
Yeah it currently wants the path to nixpkgs directly
<infinisil>
Hm does flakes have no way of doing that actually?
<bqv>
no that's possible, easily
<bqv>
inputs.nixpkgs (or whatever it is) will just be a nixpkgs tree
<infinisil>
Ah I see
<bqv>
but then it'll need manual plumbing in as a module too
<bqv>
but that can just be a module provided by nixus's unat.
<bqv>
*flake
<bqv>
sorry, switching between dvorak and qwerty rapidly
<infinisil>
Hm, but like
<infinisil>
Isn't then all that's needed a flake.nix that exports that function?
<infinisil>
Because you can already pass the nixpkgs
<bqv>
i think that's what i tried the other time, and the issue was to do with the use of lib.nixosSystem
<infinisil>
Oh you couldn't use that then
<infinisil>
It would just be something like `outputs.deployScript = inputs.nixus.buildDeployment { nodes.foo = { configuration = ...; nixpkgs = inputs.nixpkgs; }; }`
<infinisil>
If I had to guess
<bqv>
configuration could loopback to inputs.self.nixosConfigurations.${hostname}.config then, i guess
<bqv>
i feel like there was a deeper issue that i'm not remembering