diff options
Diffstat (limited to 'src/content/blog/2020/10/05')
| -rw-r--r-- | src/content/blog/2020/10/05/cargo2nix.adoc | 2 | ||||
| -rw-r--r-- | src/content/blog/2020/10/05/swift2nix.adoc | 5 |
2 files changed, 4 insertions, 3 deletions
diff --git a/src/content/blog/2020/10/05/cargo2nix.adoc b/src/content/blog/2020/10/05/cargo2nix.adoc index 38f3bfa..a2d478e 100644 --- a/src/content/blog/2020/10/05/cargo2nix.adoc +++ b/src/content/blog/2020/10/05/cargo2nix.adoc @@ -60,7 +60,7 @@ internal to Cargo. Try out the demo (also taken from the repo's README): -[source,shell] +[source,sh] ---- pushd "$(mktemp -d)" wget -O- https://euandre.org/static/attachments/cargo2nix-demo.tar.gz | diff --git a/src/content/blog/2020/10/05/swift2nix.adoc b/src/content/blog/2020/10/05/swift2nix.adoc index 4e0ae36..ba0125f 100644 --- a/src/content/blog/2020/10/05/swift2nix.adoc +++ b/src/content/blog/2020/10/05/swift2nix.adoc @@ -15,6 +15,7 @@ I wrote a simple little tool called {swift2nix}[swift2nix] that allows you trick Swift's package manager into assuming everything is set up. Here's the example from swift2nix's README file: +[source,nix] ---- let niv-sources = import ./nix/sources.nix; @@ -143,7 +144,7 @@ This is something that {node2nix}[node2nix] does right. It allows you to build the Node.js environment to satisfy NPM, and you can keep using NPM for everything else: -[source,shell] +[source,sh] ---- ln -s ${node2nix-package.shell.nodeDependencies}/lib/node_modules ./node_modules npm test @@ -165,7 +166,7 @@ nice-to-have. swift2nix itself could provide an "easy" interface, something that allows you to write: -[source,shell] +[source,sh] ---- nix-build -A swift2nix.release nix-build -A swift2nix.test |