Skip to content

Reserved crate test doesn't check the [lib] key, which is the actual important part #1904

Open
@Manishearth

Description

@Manishearth

We have a bunch of reserved crates, many of which come from internal rustc crates that Rust ships with. Using one of these names has the potential to cause a "multiple sources for dependency" clash.

However, we don't check the [lib] key in Cargo.toml, so you can still name a crate one thing and clash its actual crate name, which will lead to the same kind of problem.

This seems to be an oversight, and we should at least warn for these (ideally, error for new publishes)

Metadata

Metadata

Assignees

Labels

A-publishC-bug 🐞Category: unintended, undesired behavior

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions