Thanks for trying to update lang/ocaml. Have you seen https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218333 ?

In D19318#413631, @tobik wrote:

Thanks for trying to update lang/ocaml. Have you seen https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218333 ?

I had not but I saw that needs some update, inclusive to add a CAMLP5 variable (it is in the newest patch). But that is something I will probably need some help. ^^

[EDIT]
Oh, portmgr is already on it.

Thank you for pointing to it.

Building with GCC8 doesn't change the warnings and errors.

-nox11 should be removed and converted by using FLAVOR.

I hate to say this but I highly recommend you to work on this using github or similar because the final version of the patchset will be too long to review. My last attempt to update OCaml and related software in PR 182918 involved 100 ports and >12000 lines in the diff delta. It is old but not completely obsolete. Especially please consider to adopt migration from Mk/bsd.ocaml.mk to Mk/Uses/ocaml.mk in the patchset or update bsd.ocaml.mk to include OCaml toolchains from the first place. Uses/ocaml.mk is to maintain consistency of build/runtime dependencies and to avoid manual addition of something like "BUILD_DEPENDS=ocamlbuild:devel/ocaml-ocamlbuild" into Makefile, which makes difficult to maintain the port.

In D19318#415205, @hrs wrote:

-nox11 should be removed and converted by using FLAVOR.

I hate to say this but I highly recommend you to work on this using github or similar because the final version of the patchset will be too long to review. My last attempt to update OCaml and related software in PR 182918 involved 100 ports and >12000 lines in the diff delta. It is old but not completely obsolete. Especially please consider to adopt migration from Mk/bsd.ocaml.mk to Mk/Uses/ocaml.mk in the patchset or update bsd.ocaml.mk to include OCaml toolchains from the first place. Uses/ocaml.mk is to maintain consistency of build/runtime dependencies and to avoid manual addition of something like "BUILD_DEPENDS=ocamlbuild:devel/ocaml-ocamlbuild" into Makefile, which makes difficult to maintain the port.

I was willing to do that using the new ocaml.mk but I wasn't sure how compatible the final version would be with the actual prototype, and so I decided to work using the old (to get the things working), and later move to the new Mk when thta was done. About moving to somewhere I was indeed thinking about the same.

Thank you.

I just have noticed it would possible to aquire OCaml with a BSD Style LICENSE paying a reasonable small fee (3.500€) to become part of the Caml Consortium.

In D19318#415233, @rigoletto wrote:

I've updated the revision summary to include the GitHub address I will be working with the OCaml ports[1].

I will keep updating OCaml itself in here from time-to-time since this is the main thing, and for better internal visibility.

Thank you.

[1] currently it was no changes over the FreeBSD official ports tree but I will move the present changes to there ASAP.

Thank you. I will work on updating the old patchset in the PR to the latest ports tree and send pull requests to your github repo to avoid duplicate work if you do not mind it.

In D19318#415236, @hrs wrote:

In D19318#415233, @rigoletto wrote:

I've updated the revision summary to include the GitHub address I will be working with the OCaml ports[1].

I will keep updating OCaml itself in here from time-to-time since this is the main thing, and for better internal visibility.

Thank you.

[1] currently it was no changes over the FreeBSD official ports tree but I will move the present changes to there ASAP.

Thank you. I will work on updating the old patchset in the PR to the latest ports tree and send pull requests to your github repo to avoid duplicate work if you do not mind it.

I've added you as collaborator. IDK how GitHub works on that but later I will look if I need to do anything more to give you write access.

@mat

Several of ocaml-* ports have this license: LGPL[v2+] with linking exception. What would be the best way to handle them, just set

LICENSE=LGPL20+

or

LICENSE=LGPL20+
LICENSE_NAME=LGPL with linking exception

or other?

Thank you.

In D19318#416607, @rigoletto wrote:

@mat

Several of ocaml-* ports have this license: LGPL[v2+] with linking exception. What would be the best way to handle them, just set

LICENSE=LGPL20+

or

LICENSE=LGPL20+
LICENSE_NAME=LGPL with linking exception

or other?

Thank you.

I have no idea what "LGPL with linking exception" changes from the normal "LGPL", I always thought the LGPL was the GPL with a linking exception.

In D19318#418720, @mat wrote:

I have no idea what "LGPL with linking exception" changes from the normal "LGPL", I always thought the LGPL was the GPL with a linking exception.

This is about the generated binaries by the compiler, and not the compiler it self.

Eg. GCC-GNAT and Adacore-GNAT (free version)

• GCC-GNAT - with GCC Runtime Library Exception: generated binaries can be released with any license, including proprietary
• Adacore-GNAT - without GCC Runtime Library Exception: generated binaries are GPLv3

They are the exactly same compiler but with 9 months delta, being the Adacore on the newer.

@hrs

a few things to be considered to be added/fixed to/in ocaml.mk:

1. STRIP= #empty is needed quite often
2. ocaml-dune build system is also quite required by several ocaml ports now
3. ports using ocaml-dune install documentation in /usr/local/doc by default, and seems to bring other problems too.

Thanks.

@hrs

Since the ocaml.mk is not done yet, and now there is the dune build system become the de facto standard, I would like to suggest you a different approach: wrapping Opam into the ports system like is being done with Cabal/Haskell.

See D19730.

Thank you.

Exp-run re-requested in PR 218333 — update to version 4.05.0, to set a foot for the next changes.