diff options
Diffstat (limited to '')
| -rw-r--r-- | _articles/2020-10-05-swift2nix-run-swift-inside-nix-builds.md | 4 |
1 files changed, 2 insertions, 2 deletions
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 7960b8b..dad4334 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 @@ -119,7 +119,7 @@ Instead a much saner approach could be: filesystem layout with dependencies (i.e. exposing what the package manager expects to find), let's call it `local-registry.json`; 4. if a `local-registry.json` was provided, do a build using that. Otherwise - generate its own, by downloading the dependencies, arranging them, etc. + generate its own, by downloading the dependencies, arranging them, *etc.* The point is just making what the package manager requires visible to the outside world via some declarative data. If this data wasn't provided, it can @@ -185,7 +185,7 @@ Package managers should provide exact dependencies via a data representation, i.e. lockfiles, and expose via another data representation how they expect those dependencies to appear on the filesystem, i.e. `local-registry.json`. This allows package managers to provide an API so that external tools can create -mirrors, offline builds, other registries, isolated builds, etc. +mirrors, offline builds, other registries, isolated builds, *etc.* "\*2nix" tools should build simple functions that leverage that `local-registry.json`[^local-registry] data and offload all the rest back to the |