diff options
| author | Pjotr <wrk@bosa.lan> | 2026-11-16 10:07:04 +0000 |
|---|---|---|
| committer | Pjotr <wrk@bosa.lan> | 2026-11-16 10:07:04 +0000 |
| commit | 744278e9881db1b9cd544fb8061bb616b9020886 (patch) | |
| tree | 173105b0c5f70b29b707230a21c6911ff79ccaaf /schema.sql | |
| parent | c7bcd32190f0355ad3d6ba5a87ca7eec3fcf2604 (diff) | |
| download | ai-memory-744278e9881db1b9cd544fb8061bb616b9020886.tar.gz | |
install.sh: build, root and link, so no store path is ever written down
guix build -f guix.scm prints a path that changes with every rebuild of the tree, so the practical way to use it has been to copy a store hash into a script -- and a copied hash outlives the source. That is not hypothetical: a store on this box was created by a binary that predated the gist column, and the mismatch surfaced as an empty 'sql error (Error):' at write time. scripts/install.sh builds from this checkout, GC-roots the result (AI_MEMORY_ROOT, default ~/.local/state/ai-memory/root) so a guix gc cannot take it away, links AI_MEMORY_LINK (default ~/.local/bin/ai-memory) so nobody has to remember a hash, and then runs the binary once to prove it starts. Two builds in a row give the same store path, which is what makes the root stable between runs and not merely between rebuilds of the same day. README and doc/SKILL.md now lead with it, and keep the bare guix build as the unpinned alternative.
Diffstat (limited to 'schema.sql')
0 files changed, 0 insertions, 0 deletions
