Post by @urushitan@kakera.kintsugi.moe

@urushitan@kakera.kintsugi.moe

2026-10-25 20:23 UTC

yes, but to manually build packages against libraries yourself would be a nightmare of tooling without cargo. It’s no different than every base-devel and similar package requiring cmake because sure, you could manually run the c/c++ compilers and linkers yourself against every single folder, passing in the flags yourself, but that would take an obscene amount of time to manually build and run every compiler command yourself wiki.debian.org/Rust Debian builds it’s own local cargo registry by default. If your distro provides “pinned versions” like a said, you won’t need rustup, but you’ll still need cargo to do anything beyond a tiny project with no imports, unless you plan on writing async/http/encryption libraries all yourself.

Replies (1)

@thingsiplay@lemmy.ml 2026-10-25 20:29

It would be similar to how we build C with make or any other language, using a Makefile in example. In example if the project contains all dependencies in the Git repository already and does not need to download extra dependencies. The Makefile and configuration would handle all of that. Or for projects that do not require dependencies, it would be quite simple compiling. Debian uses cargo, which is what I would avoid. Cargo is a package manager, that is the exact thing I’m trying to avoid here with the suggestion. I think of dependencies integrated into the system package manager (pacman in example). Debian needs to do this cargo registry, because there is no other infastructure.

Open ##5244320