On 4 Sep 2022, at 19:15, Daniel Dickman <didickman@gmail.com> wrote:
>
>> On Sep 3, 2022, at 11:34 AM, Volker Schlecht <openbsd-ports@schlecht.dev> wrote:
>>
>> Hi,
>>
>> just wanted to get a quick idea about the state of affairs with OCaml in ports: there's been a lot happening in the OCaml world and not so much in the related ports.
>> Is that due to lack of time and/or interest or any more fundamental compatibility issues with the later releases?
>
> Hi Volker, nothing is stopping anyone from proposing an update.
>
> But compcert on i386 is a very important package for me so I'd like to be sure that any updates don't break it.
>
> If you decide to do any work here please be sure that all native and non-native ocaml packages continue to build and run fine.
>
> In the past I haven't been able to update ocaml without doing related updates to the many ocaml consumer ports. That being said, it is much easier these days now that the ocaml consumers in the tree were reduced to a minimum (ie. opam is expected to be used for things not in the tree).
>
> I would be very happy with newer ocaml and coq if we can get them though. (Also compcert is one version behind the latest release — that one should be an easy update I think).
Likewise, an upgrade to 4.14 in ports would be very welcome, and there should be no blockers.
OCaml 5.00 will be a bit of a bumpy ride due to the number of deprecated-features-that-have-actually-been-removed, but I use it without too many bumps on OpenBSD/amd64 these days. Daniel will be have to deal with the lack of native code i386 in OCaml 5.0 in all likelihood though -- either we have to package up OCaml 4/5 separately in ports or deal with a bytecode-only set of 32-bit architectures. We're a few months away from having to make that decision, though -- let's get the port up to 4.14 first.
cheers,
Anil
No comments:
Post a Comment