Created attachment 260424 [details] Update to 3.8.0 Update to 3.8.0 It is required by the update of coq
I did a similar thing for the same reason as wen: I updated ocaml-dune to 3.8.3 for rocq (previously coq). While there: - Move Makefile blocks for portclippy - Replace %%PORTDOCS%%share/doc/ocaml by %%PORTDOCS%%%%DOCSDIR%% in pkg-plist portlint: OK portclippy: OK poudriere: OK
Created attachment 268422 [details] Update devel/ocaml to 3.8.3
@ Benjamin Since maintainer is absent, can you possibly do a review to avoid bitrot and keep things moving?
(In reply to Daniel Engberg from comment #3) Hi Daniel, There is an outstanding issue with the current dune port that I unfortunately introduced and for which I have (still unpublished, unfortunately) fixes for. So if possible I'd recommend to hold off committing this change, and also because dune is at version 3.22.1 ATM so ports users wouldn't gain a lot from this update. The issue is that some libraries shipped by dune in $LOCALBASE/lib/ocaml/site-libs are compiled against vendored libraries and that render them unusable; e.g. the dune-glob library should be linked with devel/ocaml-re and not the vendored version. The fix is to create separate slave packages for each of those libraries, and stop installing the vendored libraries with dune. But the fix has to propagate into a couple of other the packages which actually need one of the dune libraries in addition to the dune binary. So I have better fixes in my tree (along with many ocaml updates), but I haven't been able to properly find time to cleanup the lose ends (mostly COMMENT, pkg-descr undo the ppc binutils "fixes", proper PORT_REVISION bumps, etc.) so it is always a catch-up game for me to rebase and re-update every time. The good new is that I have a bit more free time now, so I'll try to cleanup the lose ends and to approach the committers who offered me help to have all the ocaml bits committed at once.
FWIW around coq 8.20 it was still possible to build with dune 3.7 with a patch to doc/dune , see https://bugs.freebsd.org/bugzilla/attachment.cgi?id=254174 . What is preventing to use dune 3.7 now?
See also #278470 to update dune to 3.17.1 but this has likely bit-rotted already and it still doesn't fix the issue mentioned in comment #4
(In reply to Benjamin Jacobs from comment #4) Thank you Benjamin. I'll happily wait for the proper update of dune if it's in the works. My proposed patch was just a minimal way to unblock rocq, but I much prefer the solution that you propose.