Create a system to better manage .wrap files (self-hosted?)
Open
@ravi688 is already working on this.
Since Feb 8, 2025.
enhancement
- Dominant language
- C++
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Problem
We end up with duplicate .wrap files in diamond dependency relationships.
Solution
Host .wrap files at a central location. And fetch it when needed (by the build system).
Method no 1
Self-host WrapDB, some modifications might be needed in the meson itself or WrapDB. So we would maintain a fork of meson and WrapDB.
Method no 2
Use a centralized antifactory to host the .wrap files. Modify meson to use that artifactory. In that case too we would maintain a fork of meson.
Figure out which one works the best and fastest to get that working.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.