"pub extern crate" for all dependencies about quicli HOT 1 OPEN

If the dependency specifies crate = ">1.0.0, <3.0.0" and that's the only restriction, cargo will resolve to 2.∞.∞. If the binary specifies crate = "^1.0", cargo will unify the requirement to >1.0.0, <3.0.0, ^1.0.0 which is the equivalent of ^1.0.0.

The difference between the ergo "crate collection" and the quicli crate is that while ergo is just reexporting the crates it's bundling, quicli is reexporting the contents of the crates that it uses. In ergo, you're still using the the crates that it reexports. In quicli, though, though you are using the functionality of the crates quicli builds on, the existence of those crates is a secret; the reexported functionality is the functionality that quicli provides.

ergo is the only kind of crate where I'd say a crate = "*" bound is appropriate; it shouldn't be bounding the versions of the libraries the client binaries are using. But if the binary has to specify its (transitive) ergo dependencies anyway in order to specify their version, what's the point of having ergo in the first place? 🤔 I think ergo's mindset works for binaries which use the lockfile, but libraries shouldn't be using it if it's taking that lighter stance towards stability of "you specify my dependency's version requirements for me".

from quicli.