Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upstreaming status #166

Open
18 of 44 tasks
Leonidas-from-XIV opened this issue May 4, 2022 · 0 comments
Open
18 of 44 tasks

Upstreaming status #166

Leonidas-from-XIV opened this issue May 4, 2022 · 0 comments

Comments

@Leonidas-from-XIV
Copy link
Contributor

Leonidas-from-XIV commented May 4, 2022

This is a tracking issue to see the status of upstreaming dune support to the projects that we currently have overlays for. In general we want as few packages to need overlays as possible

B0:

  • asetmap (uses b0)
  • astring (uses b0)
  • bos (uses b0)
  • cmdliner (uses b0, but has dune file available so we just change the opam metadata)
  • fmt (uses b0)
  • fpath (uses b0)
  • jsonm (uses b0)
  • logs (uses b0)
  • mtime (uses b0)
  • ptime (uses b0)
  • react (uses b0)
  • rresult (uses b0)
  • uchar (uses b0)
  • uucp (uses b0)
  • uuidm (uses b0)
  • uuseg (uses b0)
  • uutf (uses b0)
  • webbrowser (uses b0)
  • xmlm (uses b0)

So there are 19 packages that use b0 that could profit from an automated dune-file generator. A few packages needs new releases but the dune support is in place. A few PRs are in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant