commit 9d8493112e58cdd1cc8c79ffb7bc390dc48b1c28
parent e088e690bee18a35e350bc16c6dd677ba4c69eaf
Author: Vincent Demeester <vincent@sbr.pm>
Date: Sat, 23 May 2020 12:48:53 +0200
builds: update fedora (add sudo)
Signed-off-by: Vincent Demeester <vincent@sbr.pm>
Diffstat:
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/.builds/fedora.yml b/.builds/fedora.yml
@@ -5,7 +5,7 @@ sources:
- git@git.sr.ht:~vdemeester/secrets
tasks:
- setup: |
- dnf install -y tar gzip
+ sudo dnf install -y tar gzip
- install_nix: |
set -euo pipefail
curl -L https://nixos.org/nix/install | sh
diff --git a/README.md b/README.md
@@ -91,7 +91,7 @@ soon-ish 👼):
Most of the `make` commands will try to populate this ahead of time. The assumption is :
have a `sync` folder where the assets are. *Note: how to bootstrap (as syncthing will
not be there, and the `sync` folder either)*
-- `docs`: holds documentation about this code, literate configuration, see [literate configuration](#org4450dda).
+- `docs`: holds documentation about this code, literate configuration, see [literate configuration](#org1e494b0).
`make publish` will publish the `README.org` and the `docs` folder to my website.
- `lib`: shared code used during configuration (mostly `nix` code).
- `machines`: configuration per machines
@@ -101,7 +101,7 @@ soon-ish 👼):
- `private`: holds non-shareable code, like *secrets*.
- `tmp`: things to… organize (e.g. where I import my other *legacy* configuration)
-<a id="org4450dda"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
+<a id="org1e494b0"></a>As I'm slowly, but <span class="underline">surely</span>, going to have `org-mode` files for
literate configuration files in this repository, I have to think of how to organize files
in order to end up with one huge file. The goal of having those `org-mode` files, is
mainly to document my configuration and publish it, most likely on [sbr.pm](https://sbr.pm).
