Orkuncakilkaya
470971bf70
The install root is not only the artifact: `ludic add` caches fetched packages in <root>/store, keyed by content hash. install_staged moved the whole root aside and replaced it, so re-running the installer — which is exactly what `ludic upgrade` does — deleted the cache and forced every project to refetch. The store is moved into the staged tree before the swap. Nothing else in the root is preserved, because everything else is the toolchain and should be replaced. Verified by staging an install, planting a store entry, upgrading, and reading the entry back. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
6 lines
337 B
Markdown
6 lines
337 B
Markdown
bump: patch
|
|
type: fix
|
|
An upgrade keeps the package store. The installer replaces the whole install
|
|
root, and `ludic add` caches packages in `~/.ludic/store` — so re-running the
|
|
one-liner deleted every package a project had fetched. The store is carried
|
|
across now; everything else in the root belongs to the toolchain and is replaced.
|