Nix is hard to learn. The concepts used are almost the same, but different. That's because it's solving slightly different problems than package managers currently do.
As the overriding example shows, the versions are pinned by hash and are stored in a file. What about it is not maintainable or scalable?
Not only me.
> That's because it's solving slightly different problems than package managers currently do.
We keep hearing this claim, and hardly any proof of that.
> As the overriding example shows, the versions are pinned by hash and are stored in a file. What about it is not maintainable or scalable?
1. Commit hashes are not versions
2. Hunting down every commit hash of every package to pin down the exact version is neither maintainable nor scalable
I believe flakes will make this a lot easier, but it's not quite here yet.
Somewhat, I guess? It will apparently let you write this:
{
inputs = {
home-manager.url = "github:nix-community/home-manager";
};
}
where you can manually point to a specific commit/branch for a tool.Better than nothing, I guess :)
What is "the same level"?
> You can pin ruby to exact version you want with https://nixos.wiki/wiki/Overlays
That page says: "Overlays provide a method to extend and change nixpkgs"
I don't want to change something. I want to simply pin a version. This is neither simple, nor scalable, nor maintainable (also here: https://news.ycombinator.com/item?id=28591202):