Listing dune targets and where they come from
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
Desired Behavior
When projects grow, dune targets are likely to be spread over multiple dune files. Sometimes, multiple dune files will contribute to a single target, eg. an installation sections. After a while, it is sometimes difficult to figure out and locate all the dune files that participate in building some alias or target.
It would be very nice if dune could report on which dune file contributes to some/all aliases and targets.
Example
$ dune about @install
src/dune: package A
share/dune: share section
[...]
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
Start with the proposed dune about @install command and review how multiple dune files can contribute to an alias or target. The issue's example shows the expected source-file and contribution reporting; done means users can identify which dune files contribute to the requested targets or aliases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100