Installation instruction in tutorial fails when using `snap` to install `rustup`.

[tothambrus11]

I installed my rust toolchain via rustup (sudo snap install rustup --classic, then install the default stable toolchain.

When executing the installation command recommend in nextest's tutorial, I get the following error:

curl -LsSf https://get.nexte.st/latest/linux | tar zxf - -C ${CARGO_HOME:-~/.cargo}/bin
tar: /home/ambrus/.cargo/bin: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
curl: (23) Failure writing output to destination

My rustup installed cargo here: /snap/bin/cargo.

It would be useful to create either a less intrusive setup process or the setup script detecting common cargo paths or using $(which cargo) in the tutorial instead of a hardcoded path.

[sunshowers]

(It's not a script — it's deliberately a single command, because that is lower risk than a script.)

I think for exotic scenarios like snaps you can extract it yourself to anywhere in your PATH.

[tothambrus11]

Snap is the default thing that ubuntu suggest when rustup is missing, so it's likely that people end up here. I was confused also because CARGO_HOME variable is not set. If there is no specific reason why you would want this tool to be extracted in .cargo/bin (which I still have no idea where is located on my machine), then saying that it's a standalone executable is enough.
It could be nice to distribute the binaries through some package managers that can automatically make the binary globally available, such as npm, pip, system package managers, or maybe cargo.

[sunshowers]

You can extract it anywhere to your PATH. .cargo/bin is just the location most people have available.

If you cargo install something with snap, where does it end up?

It could be nice to distribute the binaries through some package managers that can automatically make the binary globally available, such as npm, pip, system package managers, or maybe cargo.

Most of these, I don't want to take on the support burden of ensuring they work in perpetuity.

cargo doesn't have a way to do binary installs. A from-source install with cargo install --locked works.

[tothambrus11]

E.g. rustc is in /snap/bin/rustc.

[sunshowers]

Yes but rustc is presumably shipped with the snap, right? it'll be a rustup shim.

The question I have is: what happens if you do cargo install --locked cargo-nextest? Where does the cargo-nextest binary end up?

[tothambrus11]

It was installed in ~/.cargo/bin/cargo-nextest. It seems that this was intended to happen using the script in the tutorial. Maybe the real problem was that I was using zsh, not bash.

[hiSandog]

The tutorial should probably call out the snap rustup caveat directly instead of leaving users with a failed install command. A small install-docs note could explain the expected rustup layout and provide the recommended non-snap installation path. If nextest can detect the snap layout, an actionable error message would be even better than only fixing the tutorial.