You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
stdcompat (Update dune port thierry-martinez/stdcompat#16, wrote an email to the maintainer on 1st of June, got the fixes merged so future releases should only ever need the opam file patched)
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.
The text was updated successfully, but these errors were encountered:
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
bheap
(uses dune upstream)camlzip
(build with dune xavierleroy/camlzip#31)charInfo_width
(Upstream uses dune, consider dropping our 1.1.0 ports)ctypes(-foreign)
([wip] Port to Dune yallop/ocaml-ctypes#588)cudf
(PR available by @kit-ty-kate, released as 0.10)dose3
(Upstream usesdune
)dum
(Adddune
build files mjambon/dum#1)extlib
(Add a dune file and a new package extlib_wrapped ygrek/ocaml-extlib#54 (not by us, stalled), Postdune
build cleanups ygrek/ocaml-extlib#59 using our port, dune support merged)ocamlfind
hacl-star(-raw)
hashcons
(Upstream uses dune, needs release: Release with dune build system backtracking/ocaml-hashcons#6, wrote an email to the maintainer on 1st of June)inotify
(Upstream uses dune, needs release: new release whitequark/ocaml-inotify#17)menhir*
(uses dune upstream)ocamlgraph
(upstream uses dune)num
(comes with dune build files, but opam metadata needs to be changed to use it. PR to use dune in OPAM: Usedune
when installing via OPAM ocaml/num#28)ocp-ocamlres
(Port to dune OCamlPro/ocp-ocamlres#8)ocplib-json-typed
(Add a basic dune-project file OCamlPro/ocplib-json-typed#37 but project is deprecated)opam-*
(Upstream uses dune)ppx_tools
(Upstream uses dune)reactiveData
(uses dune upstream)seq
(uses dune upstream)sexplib
(uses dune upstream)stdcompat
(Updatedune
port thierry-martinez/stdcompat#16, wrote an email to the maintainer on 1st of June, got the fixes merged so future releases should only ever need theopam
file patched)textwrap
(Upstream uses dune upstream, needs release: Release withdune
support superbobry/ocaml-textwrap#3, wrote an email to the maintainer on 1st of June. @Leonidas-from-XIV got granted repo access and created the 0.2.1 release: [new release] textwrap (0.2.1) ocaml/opam-repository#21474)zarith
([build] [wip] Support for the dune build system. ocaml/Zarith#73 not by us)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.
The text was updated successfully, but these errors were encountered: