`cargo package --package` includes all packages if no match is found about cargo HOT 2 OPEN

It looks like this has been an issue since cargo package gained the -p flag.

I think the issue is around here. The members_with_features function has a peculiar behavior when given a spec that is not a workspace member. It will return all workspace members, because that behavior is needed for doing resolution (and handling the case where cargo build -p some_dependency is used). There probably should be some function similar to members_with_features or a separate argument that will generate an error if any of the specs does not match a workspace member.

This is sort of similar to #10677 (#10536), though publish behaves differently because it is restricted to just one package. I believe that was fixed by adding specs[0].query(member_ids)?;. members_with_features might be better suited to enforce that?

We might want to audit to see if there are any other commands that are only intended to work on workspace members have similar problems.

from cargo.