QuickRust installed by a package manager stays where the package put it, and is the QuickRust
that runs. qrust setup links ~/.qrust/bin to the package’s qrust instead of copying it
there, through the path that outlives each version, and replaces a copy an earlier setup left.
brew upgrade quickrust, apt upgrade or dnf upgrade then updates the QuickRust in use.
Before, setup copied itself, so a machine held two qrusts: the package manager upgraded one
that nothing ran, and a shell that found the package’s first reported QuickRust as never set
up. Run qrust setup once after upgrading to this release to make the link.
qrust self update and qrust self uninstall name the package manager’s command for a
package install and change nothing.
Installed from an archive or built from source, the copy in ~/.qrust/bin is the installation,
as before. Its setup does not replace a package install’s links.
qrust doctor names every qrust or cargo ahead of QuickRust’s on PATH that is another
program, and the startup-file line that puts its directory there.
Documentation
QuickRust’s documentation is available in Italian.
Updating on Windows
A Windows machine set up by one QuickRust release updates to the next. QuickRust’s cargo
and the other toolchain programs in its bin are copies of qrust on Windows, and
qrust self update and qrust setup took the copies an earlier release had made for
someone else’s programs and stopped: C:\…\bin\cargo.exe exists and is not QuickRust.
QuickRust now records every binary it installs and recognises copies of each; a program
that is not QuickRust’s is still never overwritten.
An install that stopped there can be finished by running the new release’s qrust setup.