caml-list - the Caml user's mailing list
 help / Atom feed
From: Muriel SHAN SEI FAN <>
Subject: Re: [Caml-list] 300$ Bounty for the feature compilation cache in opam
Date: Thu, 18 Jun 2020 13:18:27 +0200
Message-ID: <> (raw)
In-Reply-To: <>

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

Thank you Fabrice and Louis.
As other institutions or individuals on this list, you know that we are
happy (as a company /and/ as individuals) to contribute to the thriving
of the OCaml community. All initiatives are good to take :-)

On 18/06/2020 11:09, Louis Roché wrote:
> I was happy to give 300USD of my personal money to push someone to
> work on this task. But I can't afford to pay a company to work on that
> task.
> There is a script in the opam repo providing binary cache already[1].
> The problem is that it doesn't handle relocation well. Because of
> paths contained in the cached content. For example if I install ocaml
> in a switch A, then in switch B, then delete the switch A, suddenly
> the switch B won't work anymore.
> To me the ideal solution would be to extract the code of esy that is
> doing path replacements and use it in an opam hook. It would also
> require all switches to be installed in a path of a similar length,
> but that's a trivial task.
> 1.
> On Thu, Jun 18, 2020, at 17:00, Fabrice Le Fessant wrote:
>> 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.
>> --
>> Fabrice LE FESSANT
>> CEO Origin-Labs SAS & Dune Network
>> Le jeu. 18 juin 2020 à 03:53, Francois Berenger <
>> <>> a écrit :
>>     Cf.
>>     for details.
>> -- 
>> Fabrice LE FESSANT
>> Chercheur en Informatique
>> INRIA Paris Rocquencourt -- OCamlPro
>> Programming Languages and Distributed Systems

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

  parent 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
2020-06-18  9:10         ` Louis Roché
2020-06-18  9:23           ` Gabriel Scherer
2020-06-18 11:18           ` Muriel SHAN SEI FAN [this message]
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