6 ms·
The final accepted version of that RFC makes no mention of this, and even contemplates Cargo install as an alternative to system package managers [1]. The comm
by kd5bjo 6y ago
The final accepted version of that RFC makes no mention of this, and even contemplates Cargo install as an alternative to system package managers [1].
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-cargo-install.md#system-package-managers https://github.com/rust-lang/rfcs/blob/master/text/1200-carg...
- svnpenn 6y agoEven if you're right, what are you arguing here? "Cargo build" makes it extremely easy to distribute executables, as do GitHub releases. And free I might add. 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".
- kd5bjo 6y ago> It it only the most lazy and selfish developers who would not utilize this. 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.
- fluffything 6y ago> It it only the most lazy and selfish developers who would not utilize this. 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.