Skip to content

v0.15.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 04:01
· 8 commits to main since this release

Four more toolchains

The same five steps move four more families: Ruby, Composer, NuGet, and the
caches that download and build tools keep.

Provider What moves Switch
ruby The Bundler cache, and the cache of every user gem folder Symbolic link for each folder
composer The download cache Symbolic link
nuget The global package folder Symbolic link
devtools Electron downloads, node-gyp headers, and the tsc cache Symbolic link for each folder

A gem folder carries the Ruby version in its name, so the scan finds the
folders each time. Each folder keeps an ID from its path, so a scan never
renames a cache that the ledger holds.

BUNDLE_USER_CACHE, COMPOSER_CACHE_DIR, and NUGET_PACKAGES name a folder
that the link replaces. The variable still names a path that works, so a move
does not refuse it.

The rail gains a Ruby group. Composer, NuGet, and the dev tool caches show
under Other.

devtools names no process. node runs long-lived programs, so a lock on it
would stop a move on a machine that builds nothing. Stop the build before the
move.

Evidence

A move of all seven caches in a test home folder:

$ exodrive migrate --target=/tmp/exo-c/drive --tools=ruby,composer,nuget,devtools
==> Migrating Bundler Cache (…/.bundle/cache, 4.0 KB) by symbolic link...
✅ Migrated Bundler Cache.
==> Migrating RubyGems Cache (3.3.0) (…/.gem/ruby/3.3.0/cache, 4.0 KB)…
✅ Migrated RubyGems Cache (3.3.0).
Migration completed. Reclaimed 28.0 KB on the local disk.
$ ls -l ~/.bundle ~/.gem/ruby/3.3.0 ~/.nuget ~/Library/Caches
cache -> /tmp/exo-c/drive/ruby/bundler-cache
cache -> /tmp/exo-c/drive/ruby/gem-cache-bfea8de3
packages -> /tmp/exo-c/drive/nuget/packages
composer -> /tmp/exo-c/drive/composer/cache
electron -> /tmp/exo-c/drive/devtools/electron
node-gyp -> /tmp/exo-c/drive/devtools/node-gyp
typescript -> /tmp/exo-c/drive/devtools/typescript

$ exodrive verify --all
[ok] composer.cache: /tmp/exo-c/drive/composer/cache (1 file, 4.0 KB)
[ok] devtools.electron: /tmp/exo-c/drive/devtools/electron (1 file, 4.0 KB)
[ok] devtools.node-gyp: /tmp/exo-c/drive/devtools/node-gyp (1 file, 4.0 KB)
[ok] devtools.typescript: /tmp/exo-c/drive/devtools/typescript (1 file, 4.0 KB)
[ok] nuget.packages: /tmp/exo-c/drive/nuget/packages (1 file, 4.0 KB)
[ok] ruby.bundler-cache: /tmp/exo-c/drive/ruby/bundler-cache (1 file, 4.0 KB)
[ok] ruby.gem-cache-bfea8de3: /tmp/exo-c/drive/ruby/gem-cache-bfea8de3 (1 file, 4.0 KB)
Checked 7 copies. Every copy matches its move.

A changed file in one copy reads as changed, and the command exits 1. Every
rollback restored a real folder and removed its record. The ledger was empty
again.

What this release does not prove

This Mac holds none of the seven folders, so the evidence above comes from a
test home folder. The scans on this Mac found no cache of these tools. That is
the same rule as before: a folder that does not exist has no row.

The Ubuntu job failed on the first push. TestLifecycle_Devtools built the
folder under Library/Caches, which is the macOS rule only. The test now
states the platform rule itself, and it passes on Linux in a container.