New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add opam tree
subcommand to display a dependency tree
#3775
Comments
i often have install deps that fail, and i want this feature to see who is calling for it. perhaps the parent node has bad ranges, needs to be pinned, etc. |
|
Is there any way to get that kind of information, albeit not as nicely for now? I experimented with (To clarify: I know that |
Your |
@cannorin if you have some time to spend on this I'd suggest to look at this paper which seems to have interesting techniques for ASCII DAG visualisations. |
@dbuenzli I've just read the paper. Looks interesting for sure, but it would need some additional work to allow annotating edges, which would be needed to show the constraints (e.g. |
opam query
only shows flat results.opam tree
, similar tocargo tree
in Rust, would display a dependency tree. Here's how it looks like in Rust:Note the Unicode-art.
Items marked with (*) are later instances of common subtrees; the subtrees are skipped instead of being printed another time.
Useful options:
--duplicate
This displays a forest of inverted trees, starting at every duplicate dependency, towards the root.
This is useful for examining how dependency versions get constrained.
The text was updated successfully, but these errors were encountered: