Crates.io "first-come, first-served" for plain crate names - why and how should it be changed?

tools and infrastructure cargo
19

So the only two changes being proposed here are

  • Display/treat lib.name more prominently on crates.io, and
  • Nudge package culture to be more accepting of package.name != lib.name,

yeah? Because everything else already functions; myorg-foo = "1.0" already gives you ::foo as the extern crate name when the dependency renaming syntax ([dependencies].foo.package) is not used.

7 Likes