Félix Saparelli

hmm, that's weird that i didn't catch it earlier, but something is really broken here still. Terribly sorry! you'll have to install sccache another way for now, I don't think...

That feels very much like building an entire feature just for a single package, and is strongly departing from the `.cargo` usage. Additionally, on Windows, it's my understanding that DLLs...

I think let's park this for now until we have some other project that wants it, and that could help inform the approach to take, or we're ready to really...

hi, please don't use 0.13.0, and stick to 0.12.0 for now; we've unreleased 0.13.0 due to other such issues (#370) and will release 0.13.1 once we've got definitive fixes for...

There is also no default for the `pkg-fmt` in 0.13, the default is "guess". We'll improve the help messages. (#378)

For your case, use this: ```console $ cargo binstall fnm \ --pkg-url="https://github.com/Schniz/fnm/releases/download/v1.31.1/fnm-arm64.zip" \ --pkg-fmt Zip \ --bin-dir '{ bin }' ```

`--bin-dir` is not where things are installed, that's `--install-path`. `--bin-dir` is where the binaries are in the archive (it's also misnamed, and should be `bin-path`, as it's the full path...

We should definitely guard against looking outside the archive when doing those operations (#379) but technically binstall did do what you told it to. Kind of.

> any way to tell binstall not to append version to binary? Ack! Yeah, `--no-symlinks` really should do that instead of the current thing. I'll open up a new issue...

Binstall, unlike a more traditional/proper package manager, mostly relies on guessing rather than an authoritative manifest for packaging. We could probably add a binstall metadata option to override the packaged...