Ouput Resolution of Pins
Open
Nobody has claimed this yet.
package management
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
When solving for a build plan, we print all the packages and their selected versions. Whenever we select a version of a package using the pin stanza or pin-depends, we should output the chain of responsibility that caused this pin to be pulled. E.g.
- foo.0.1.0 (git+https://github.com/ocaml/foo.git)
introduced by bar.0.1.0 (git+https://...)
introduced by baz.0.1.0 (a/dune-project 12:45)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing build-plan package selection for the pin and pin-depends cases, then identify how dependency provenance is represented. Done means selected pinned versions include an indented chain showing which packages or project locations caused each pin to be pulled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100