But if Cargo is the only package available with rustc The package is actually called “rust”, “rust” is the only package available with rustc (and cargo): archlinux.org/packages/extra/x86_64/rust/files/ Then we can’t make the argument I absolutely can make the argument I made. The argument was that you need to have rustc to use cargo, because cargo uses rustc, and this means that assuming rustc exists is a lot safer than assuming that cargo exists… because if cargo is installed then it follows that rustc must be installed too. And this is true in all distros, not specific to Archlinux, which is why it’s a more universal assumption than yours. There are many ways of compiling Cpp, even without using a package manager There are many ways of using rustc too. Cargo the officially recommended method, so naturally is very popular. I still don’t think the packaging in archlinux should be attributed the merit of the popularity of cargo…