We currently don't ship any development tools for rust (rustfmt, clippy and many more), as well as the source code of the standard library. I propose to create a rust-devel package including what I mentioned, so that users will be able to use Solus-provided rust for development just as expected.
Depends on T10315.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T10316 Create a rust-devel package | |||
| Open | None | T10315 Include cargo into the rust package and deprecate cargo package |
Can you explain why we wouldn't just put these into the main rust package? From what I can tell, our rust package doesn't get binary linked to by other packages. Based on how it's used, rust is already a -devel package, just not in name. Seems to me that splitting the package just means one more thing for devs to install.
Practical rationale
rustfmt, clippy and the stdlib source code are heavyweight. By providing a different -devel package, we can avoid installing unwanted tools when one (this "one" can also be our build server) just wants to build an application. "Want to compile? Here you are with rustc and cargo. Want to develop software? Here's the toolchain you need".
Philosophical rationale
-devel package is for... development. I think this respects the principle of least astonishment.