summaryrefslogtreecommitdiffhomepage
path: root/content
diff options
context:
space:
mode:
Diffstat (limited to 'content')
-rw-r--r--content/blog/where_flakes_fall_off.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/content/blog/where_flakes_fall_off.md b/content/blog/where_flakes_fall_off.md
index ca26a37..2aec88e 100644
--- a/content/blog/where_flakes_fall_off.md
+++ b/content/blog/where_flakes_fall_off.md
@@ -2,7 +2,7 @@
title = "where flakes fall off: an eval cache tale"
author = ["santi"]
description = "a lower case only blog, purely for aesthetics"
-lastmod = 2025-04-22T15:34:55-03:00
+lastmod = 2025-04-22T16:42:48-03:00
tags = ["nix", "flakes"]
draft = false
+++
@@ -150,9 +150,9 @@ $ ~/my-repo :: git log --pretty=oneline
moreover, this state is extremely fragile. if we try to add a new file to the directory, even if it's not read from the nix expression, it will invalidate the cache, because it will generate a different store path, and the git tree isn't clean anymore.
```sh
-[larissa] ~/my-repo :: touch newfile
-[larissa] ~/my-repo :: git add newfile
-[larissa] ~/my-repo :: time nix build ./a/b/c
+$ ~/my-repo :: touch newfile
+$ ~/my-repo :: git add newfile
+$ ~/my-repo :: time nix build ./a/b/c
warning: Git tree '/home/leonardo/my-repo' is dirty
real 0m0,885s