Building Private Libraries/Executables with Lock Directory
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
Private libraries and executables are those that do not belong to any particular package. However, they still need to be built and may depend on public packages. There should be a way to specify which packages are necessary to build such libraries and executables.
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 by tracing how Dune handles lock directories and private libraries or executables, then identify where dependencies for targets outside a package are specified. The work is done when private targets can declare the public packages needed to build them and the lock-directory workflow resolves those dependencies.
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
- Needs clarification
- Newbie friendliness
- 25/100