That's why using package sets (or whatever you want to call them) is a necessity with such packages like crates. The set of 'most important' (whatever that mean

That's why using package sets (or whatever you want to call them) is a necessity with such packages like crates. The set of 'most important' (whatever that means ;) packages in versions that are _tested_ to work together. So that you do not end with broken dependencies like needing package A in a version <d and >d at the same time. Haskell 'does' this with their LTS and nightly package sets: https://www.stackage.org/snapshots https://www.stackage.org/snapshots Without such a curated set of packages I've eventually run into unresolvable dependencies with ever package manager and language used by me.