Please note that "cargo install" is intended for installing Cargo subcommands and Rust-related tools for developers, not for distributing general software to end-users. https://github.com/rust-lang/rfcs/pull/1200#issuecomment-120...
The comment you link uses Rust tools as a justification for adding “cargo install”, but doesn’t attempt to limit its applicability to other binaries.
[1] https://github.com/rust-lang/rfcs/blob/master/text/1200-carg...
It it only the most lazy and selfish developers who would not utilize this. I am speaking as someone who has distributed both Rust and Go programs.
Even a once a year executable release would be better than just saying "build it yourself".
Please refrain from making ad-hominem attacks on people that make different decisions than you would, even if they’re anonymous.
Open-source developers make their own decisions for their own reasons. They donate their time and effort to provide something to the community, and only they are in a position to determine what activities are worth their time.
Are you calling the whole Gentoo community lazy ?
If anything, I'd consider them to be the opposite of lazy, since making sure that all software always builds properly on each of your users machines takes a lot of work (IMO much harder than only making sure that it builds on your package manager controlled servers), and Watts.
FWIW the few rust devs I know do it exactly like this.
I, for one, cannot install this on the latest Debian Stable, I'm getting 'failed to parse Cargo.lock file' errors with cargo. So since there's no other way for me to install this or try this out, that's it.
Now I could probably install a more recent cargo version, but really, should I have to? I'm not a rust dev at all, and it seems like a high tax to pay for installing a tool I don't even know I will really use. I'll also know that raising a support issue about this would come off as entitled, and I'm not too familiar with Rust's ecosystem so I don't know if I step on anyone's toes, so I won't do it.
> It is expected that all major Rust projects will still invest effort into distribution through standard package managers, and Cargo will certainly have room to help out with this, but it doesn't obsolete the need for cargo install.
If you're not a Rust developer, expecting you to have cargo and the right toolchain installed is too high a burden.
You don’t have to: You always have the option of not using the tool. It’s provided for free, and it’s not reasonable to expect it to be appropriate for everyone (or really anyone except the developer).
If their chosen installation method makes it unsuitable for you, so be it.
(NB: I am not affiliated with and do not speak for this project)
I specifically stated that I do not want to raise any issues as that would be entitled behavior.