4 ms·
Hm... the flakes are still experimental. I wonder when they are going to be finally not marked as such. I switched to them exclusively (removed all nix channel
by grawp 5y ago
Hm... the flakes are still experimental. I wonder when they are going to be finally not marked as such.
I switched to them exclusively (removed all nix channels) and haven't had any troubles yet.
- aidenn0 5y agoIs there a "getting started" guide for flakes? I've been using NixOS for a few years and I'm kind of aware that flakes exist, but I'm not sure: - What problem(s) they will solve for me - How I should go about using them to solve the above problems.
- flurie 5y agoThe best overall guide for flakes is likely the one from Serokell: https://serokell.io/blog/practical-nix-flakes https://serokell.io/blog/practical-nix-flakes. In the most basic, practical sense, flakes solve the standardization and pinpointing of two things: inputs, previously solved by things like niv, and outputs, making nix structures more standard and better able to coexist. Things like overlays, package outputs, nixos configurations, and even flake templates themselves all follow the same structure. The result of all this is that, when I look at a non-flake repository, I may have to spend some time looking around to see what it does at a high level, and it may have its own special method of installation that usually begins with this = import (builtins.fetchTarball "https://...") You can start by converting any of the things I listed to flakes, and there is a module called flake-compat designed to provide backward compatibility for non-flakes. The Serokell guide is very helpful for this as well.