Skip to content
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.

Is cargo tree support workspace ? #73

Closed
Pana opened this issue Aug 19, 2019 · 2 comments · Fixed by #86
Closed

Is cargo tree support workspace ? #73

Pana opened this issue Aug 19, 2019 · 2 comments · Fixed by #86

Comments

@Pana
Copy link

Pana commented Aug 19, 2019

No description provided.

@Boscop
Copy link

Boscop commented Sep 23, 2019

Yes, please add support for workspaces. So that -d can be used to find out which crates in your workspace use different versions of the same dep.

sfackler added a commit that referenced this issue Dec 30, 2019
@sfackler
Switch to using cargo-metadata
fc8e4f4 
This both makes the crate compile way faster and avoids having to touch
tons of unstable, undocumented cargo internals. This requires Rust 1.41
(the current beta) for some cargo-metadata features.

There are some subtle differences in the new output (particularly in
handling dependencies between crates in workspaces), but they're pretty
minor.

Closes #73
Closes #69
Closes #66
Closes #65
Closes #63
Closes #61
Closes #57
Closes #20
sfackler added a commit that referenced this issue Dec 30, 2019
@sfackler
Switch to using cargo-metadata
354df7a 
This both makes the crate compile way faster and avoids having to touch
tons of unstable, undocumented cargo internals. This requires Rust 1.41
(the current beta) for some cargo-metadata features.

There are some subtle differences in the new output (particularly in
handling dependencies between crates in workspaces), but they're pretty
minor.

Closes #73
Closes #69
Closes #66
Closes #65
Closes #63
Closes #61
Closes #57
Closes #20
@sfackler sfackler mentioned this issue Dec 30, 2019
Merged
sfackler added a commit that referenced this issue Dec 30, 2019
@sfackler
Switch to using cargo-metadata
9dc0346 
This both makes the crate compile way faster and avoids having to touch
tons of unstable, undocumented cargo internals. This requires Rust 1.41
(the current beta) for some cargo-metadata features.

There are some subtle differences in the new output (particularly in
handling dependencies between crates in workspaces), but they're pretty
minor.

Closes #73
Closes #69
Closes #66
Closes #65
Closes #63
Closes #61
Closes #57
Closes #20
@luser
Copy link

luser commented Jan 27, 2020

@sfackler I assume #86 made some foundational changes to support this, but it looks like in practice you still need to specify a single package to print a tree of? cargo metadata supports being run from a workspace so presumably cargo tree could support that usecase as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch to using cargo-metadata sfackler/cargo-tree
3 participants
@luser @Boscop @Pana