caml-list - the Caml user's mailing list
 help / Atom feed
From: Fabrice Le Fessant <>
To: Francois Berenger <>
Subject: Re: [Caml-list] 300$ Bounty for the feature compilation cache in opam
Date: Thu, 18 Jun 2020 11:00:26 +0200
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

opam is maintained by OCamlPro, why not contact them and get a quote ? It
won't be 300$, but everybody will enjoy the feature in the next version.

As a side note, a long time ago, I had an implementation of a binary cache
for OPAM. The modifications in OPAM were minimal: opam would
just call a hook to build the package and install it, providing a checksum
of dependencies and sources. The checksum would be used by an external tool
(`ocp-bin`) to query the local binary cache (or a remote server) and either
re-install the package or build it and save it in the cache. Since it was
written in 2013, not sure if it would still work easily with current opam.
Its code was used later to create opam-builder.
CEO Origin-Labs SAS & Dune Network

Le jeu. 18 juin 2020 à 03:53, Francois Berenger <> a écrit :

> Cf.
> for details.
Chercheur en Informatique
INRIA Paris Rocquencourt -- OCamlPro
Programming Languages and Distributed Systems

[-- Attachment #2: Type: text/html, Size: 2726 bytes --]

  reply index

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 13:17 [Caml-list] OCaml 4.11.0, first alpha release Florian Angeletti
2020-06-04  7:29 ` [Caml-list] OCaml 4.11.0, second " Florian Angeletti
2020-06-17 15:42   ` [Caml-list] OCaml 4.11.0, third " Florian Angeletti
2020-06-18  1:53     ` [Caml-list] 300$ Bounty for the feature compilation cache in opam Francois Berenger
2020-06-18  9:00       ` Fabrice Le Fessant [this message]
2020-06-18  9:10         ` Louis Roché
2020-06-18  9:23           ` Gabriel Scherer
2020-06-18 11:18           ` Muriel SHAN SEI FAN
2020-06-29 15:25     ` [Caml-list] OCaml 4.11.0, first beta release Florian Angeletti

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror

AGPL code for this site: git clone public-inbox