From b3aae7a946565462436adba9c063c38e558773ce Mon Sep 17 00:00:00 2001 From: EuAndreh Date: Mon, 5 Oct 2020 18:06:19 -0300 Subject: swift2nix post: Remove duplicated phrases --- _posts/2020-10-05-swift2nix-run-swift-inside-nix-builds.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_posts/2020-10-05-swift2nix-run-swift-inside-nix-builds.md b/_posts/2020-10-05-swift2nix-run-swift-inside-nix-builds.md index bd889af..7960b8b 100644 --- a/_posts/2020-10-05-swift2nix-run-swift-inside-nix-builds.md +++ b/_posts/2020-10-05-swift2nix-run-swift-inside-nix-builds.md @@ -162,8 +162,8 @@ how NPM runs some things will be future-compatible, since node2nix isn't trying to replicate what NPM does, or fiddling with NPM's internal. **A "*2nix" tool should build the environment, preferably from the lockfile -directly and offload everything else to the package manager**. Everything else -is just nice-to-have. +directly and offload everything else to the package manager**. The rest is just +nice-to-have. swift2nix itself could provide an "easy" interface, something that allows you to write: -- cgit v1.2.3