From 7a35aa1128c85c94ca722ab5a1fea63adb53862a Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Tue, 20 Oct 2020 06:48:26 -0300 Subject: swift2nix article: typo by reader --- _articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md b/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md index dad4334..7b7570f 100644 --- a/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md +++ b/_articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md @@ -76,7 +76,7 @@ Package managers want to do too much, or assume too much, or just want to take control of the entire build of the dependencies. This is a recurrent problem in package managers, but I don't see it as an -inherit one. There's nothing about a "package manager" that prevents it from +instrinsic one. There's nothing about a "package manager" that prevents it from *declaring* what it expects to encounter and in which format. The *declaring* part is important: it should be data, not code, otherwise you're back in the same problem, just like lockfiles are just data. Those work in any language, and -- cgit v1.2.3