Flakes: Difference between revisions
imported>Patryk27 Rework the introduction |
imported>Patryk27 mNo edit summary |
||
| Line 19: | Line 19: | ||
''(if you're familiar with modern packages managers like <code>cargo</code> or <code>npm</code>, then the overall mechanism shouldn't surprise you - Nix works in a similar way, although without a centralized repository.)'' | ''(if you're familiar with modern packages managers like <code>cargo</code> or <code>npm</code>, then the overall mechanism shouldn't surprise you - Nix works in a similar way, although without a centralized repository.)'' | ||
Flakes are meant as a replacement for '''channels''' and things like ad-hoc invocations of <code>builtins.fetchgit</code> - no more worrying about keeping your channels in sync, no more worrying about forgetting about a dependency deep down in your tree: everything's at hand inside <code>flake.lock</code>. | Flakes are meant as a replacement for '''channels''' and things like ad-hoc invocations of <code>builtins.fetchgit</code> - no more worrying about keeping your channels in sync, no more worrying about forgetting about a dependency deep down in your tree: everything's at hand right inside <code>flake.lock</code>. | ||
== Installing flakes == | == Installing flakes == | ||