> cargo install marmite<p>I'm not the only one (1) that believes this is wrong direction for cargo, and is abusing it's intent and purpose.<p>If you want to distribute an application, there are lots of ways to do that. If it's a developer tools, for developers, `cargo install` might be suitable, sure... but I think there's a fair argument to be made that if you want a tool:<p><pre><code> git clone foo
cd foo
cargo install --path .
</code></pre>
Is an explicit, safe and less error prone way of doing it.<p>...and one that doesn't walk us down the road of (see the linked thread) the obvious desire people are going to have sooner or later to cache binary builds instead of building locally, and turn `cargo install` into some kind of binary application distribution application or app store.<p>If you don't believe me, read that thread, and the linked thread.<p>[1] - <a href="https://github.com/rust-lang/cargo/issues/13994#issuecomment-2143204956">https://github.com/rust-lang/cargo/issues/13994#issuecomment...</a>