cargo package --manifest-path foo/Cargo.toml uses foo/target instead of ./target

[SimonSapin]

When a project contains multiple crates, they have to be packaged and published separately (#849). So I’m using --manifest-path to tell Cargo which crate to publish, starting with leaves on the dependency tree.

This crates and uses a target directory next to the respective Cargo.toml, while I expected it to use the shared target at the project’s root, like e.g. cargo build does when building path dependencies. Is this a bug, or deliberate?

[alexcrichton]

I think this is a dupe of #482 as it would basically be a prerequisite for this, and this would also fall out of #482.

[alexcrichton]

As in, this is currently intended (btw)