Shouldn't mise prune or mise cache prune also remove obsolete/unused http-tarballs?

[dhanak]

Tools installed via the http backend are extracted into ~/.local/share/mise/http-tarballs/, and the installs are just symlinks to these folders with hash names. When a newer version is installed, a new tarball directory is created, but the old one isn't deleted. Nor is it removed when calling mise prune or mise cache prune. These tarball directories can pile up and occupy a significant amount of space, unnecessarily.

I can remove them manually, but because of the hash names, it needs a bit of digging to figure out which are the obsolete directories.

❯ mise dr
version: 2026.4.25 linux-x64 (2026-04-28)
activated: yes
shims_on_path: no
self_update_available: yes

build_info:
  Target: x86_64-unknown-linux-gnu
  Features: OPENSSL, RUSTLS_NATIVE_ROOTS, SELF_UPDATE
  Built: Tue, 28 Apr 2026 11:00:25 +0000
  Rust Version: rustc 1.95.0 (59807616e 2026-04-14)
  Profile: release

[jdx]

I think they're excluded since there isn't a good way to know if they're used by tool-stubs

[dhanak]

I see.

I don't know how many people use tool-stubs. The http backend, on the other hand, is definitely used by many, since it's the default backend for several tools. In other words, I'm positive that the issue caused by cumulating obsolete http-tarballs affects more people, than would the unnecessarily deleted (and then automatically refetched) tarballs.

Overall, I would still consider pruning http-tarballs, even at the potential cost of extra re-downloads.