~900 KB
The CLI, the verifier and the MCP server. Pure Python, zero third-party dependencies, Python 3.11 or newer. This is what the installer fetches.
The tool is pure Python with no third-party dependencies. It installs into your
home directory, never asks for sudo, and never edits your shell profile.
If this does not resolve, JavaScript is disabled or the release manifest is unavailable. The source-checkout instructions further down need neither.
Piping a script from the internet into a shell is trust on first use. The checksum protects the payload, not the installer. So here is the two-step form, presented as an equal option rather than a footnote.
curl -fsSLO /install.shless install.sh && sh install.shThe installer verifies the release tarball against the
SHA256SUMS published with it and refuses to install on a mismatch. It
prints both digests when that happens.
Conflating these is the main way installing Rosetta goes wrong. Only the first two come from us.
The CLI, the verifier and the MCP server. Pure Python, zero third-party dependencies, Python 3.11 or newer. This is what the installer fetches.
Real VistA MUMPS routines, the frozen benchmark split, task sets and the FileMan dictionary extract. Ships inside the same tarball, so a fresh install works with no second download.
YottaDB inside a WorldVistA container, pulled from its publisher by
scripts/bootstrap.sh. Never redistributed here. Install succeeds
without it.
rosetta demo and rosetta doctor are built to run with no container and no network, so you can see the thesis before provisioning anything.
The installer is a convenience. A checkout plus the launcher script does the same thing with nothing downloaded from a release.
git clone https://github.com/travis-hodges/Rosetta.gitbash scripts/install.sh --bin-dir ~/.local/binrosetta doctorThe launcher resolves the checkout from its own location, so
rosetta works from any directory. Keep the checkout where it is, or
reinstall the launcher after moving it.
Versions are unpacked under ~/.local/share/rosetta/ and the launcher
is a single file. Nothing else is touched, so nothing else needs cleaning up.
sh install.sh --uninstallA rosetta launcher the installer did not create is
left alone rather than deleted. The container, if you provisioned one, is removed
with docker rm -f rosetta-verify.