34
Pinning NixOS generations to the commits that built them (ikskoder.dev)
submitted 4 weeks ago by to c/nix@programming.dev
2 comments fedilink hide all child comments
 

Tired of rolling back to an old NixOS generation and having no idea which commit it was built from? Here's how to fix that: ikskoder.dev/blog/nixos-generations-git-commits

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 4 weeks ago (1 child)

never really had the issue where I don't know what commit is tied to what generation. add to the fact I might roll back once in a blue moon and if it does require a roll back I already know why I have to roll back.

That being said this is neat, I like it, but I think it's overblown for a minimal issue.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
  • [–] [S] 5 points 4 weeks ago

    Fair point) It really depends on how you use your system. If I weren't constantly tweaking things, I don't think it'd be an issue for me either.

    In my case I also use Home Manager as a NixOS module, so every home config change is a system rebuild too, and I'm at almost a thousand generations by now. When I'm trying out something new I can hit up to 50 rebuilds in a day (rare, but it happens), and that's exactly when it becomes a problem.

    So yeah, for a lot of people this is definitely overkill, but for others (similar to how I use it) it can save a lot of digging.

  • permalink
  • fedilink
  • source
  • parent