09:52 <discocaml> <peuk> Maybe the caching strategy should be different for packages that have a lot of revdeps. I don't know for other projects but in Frama-C, even we do not use Opam most of the time for our CI, it often happens that these jobs fail because either camlcity or Inria's GitLab are down. Which also means that for Opam users those packages cannot be installed.

11:41 <companion_cube> Same thing, it's still infuriating

12:55 <discocaml> <sim642> How do you avoid using opam for that? A container with pre-built dependencies or something?

13:49 <discocaml> <peuk> We use Nix. The main drawback is that we do not necessarily have the most recent version of our dependencies (since I do not update the commit frequently), but we benefit of a local cache + the nix cache which is quite comfortable. We build using Opam nightly and for releases to check that we will not have bad surprises when publishing.

22:36 <discocaml> <shon_18152> Wouldn't it be nice to set up a package source mirror(s) for the opam repo?

22:36 <discocaml> <shon_18152> Wouldn't it be nice to have (a) package source mirror(s) for the opam repo?

22:37 <discocaml> <shon_18152> Wouldn't it be nice to have (a) package source mirror(s) for the opam repo packages?

22:38 <discocaml> <yawaramin> eg Go automatically proxies all packages downloaded by the `go` tool on Google servers

22:38 <discocaml> <yawaramin> unless the user explicitly requests it not to

23:57 <companion_cube> I'd love for it to be a backup thing if the regular download fails