The OCaml Planet RSS

Feedback on this post is welcomed on Discuss! We are extremely happy to announce the release of opam 2.4.0 and encourage all users to upgrade. Please read on for installation and upgrade instructions. Major changes On opam init the compiler chosen for the default switch will no longer be ocaml-syste...

The log from an OBuilder job starts with the steps needed to reproduce the job locally. This boilerplate output assumes that all OBuilder jobs start from a Docker base image, but on some operating systems, such as FreeBSD and macOS, OBuilder uses ZFS base images. On OpenBSD and Windows, it uses QEMU images. The situation is further complicated when the issue only affects a specific architecture that may be unavailable to the user.

opam 2.4 was branched last week… very pleasing to see Ryan’s work on Nix depext support get merged (we spent quite a bit of time on that together last summer). It’s a subtle-sounding (huge) change, but the move away from relying on patch and diff as external commands (which has been a HUGE amount of work done by @kit-ty-kate) paves the way for being able to sort out the incredible slowness of opam update on Windows.

Most package managers support some pin functionality to ensure that a given package remains at a particular version without being upgraded. The stable OPAM 1.1 already supported this by allowing any existing package to be pinned to a target, which could be a specific released version, a local filesy...

Switch between OCaml compilers easily with OPAM and GitHub pull requests.

We have recently worked on modifying the OCaml system to be able to profile OCaml code on Linux amd64 systems, using the processor performance counters now supported by stable kernels. This page presents this work, funded by Jane Street. The patch is provided for OCaml version 4.00.0. If you need it...

I’ve updated my backtrace patch to work with OCaml 3.11.x as well as 3.10.x. The patch provides access to backtraces from within a...