pkg: avoid launcing external dune processes for building packages
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.9k
- Forks
- 500
- Avg merge
- 15h 21m
- Merged PRs (30d)
- 277
Description
Currently when building package dependencies that use dune, we launch a subprocess. However, as @rgrinberg noted
our end goal is not to launch any external dune processes to build packages. This is going to give us some rather significant performance improvements.
This factors our the more principled, but also more demanding work, proposed during the course of https://github.com/ocaml/dune/issues/10019 .
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
Read the linked discussion in ocaml/dune#10019 to understand the proposed principled approach and the constraints around package dependencies that use dune. The work is complete when package builds no longer launch external dune subprocesses while preserving dependency-building behavior and the stated performance goal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100