I’m in the process of converting my old nix configs to a flake-based one. The problem I see is that I have one computer tracking 20.09, another unstable. So a single flake.nix won’t track both.
I tried to put flake.lock in .gitignore, but nix tries to force commit it. Could we have a hostname-based lock system, for example, lock files are placed in locks/<hostname>.lock?
+1 for the having multiple inputs to track different channels.
If you’re trying to use a single input to point at different channels, wouldn’t that also mean you’d have to be manually switching the input’s URL between each machine every time?
But this is how you do it. Though just use the same for both… It makes it easier to compare machines if you know that software on both have the same version
Well, I guess I’m just nitpicking too much, and I agree I should try to track the same commit on all machines that use the channel.
Another similar corner case is: Mix-match between stable and unstable channel, but I guess your suggestion should also apply here: Track the same commit for both channels on all machines that use them.