Central OPAM documentation site

I think this would be a good way to make sure you can build consistent universes of documents for each opam package root, and do it efficiently. Note that disk size for the entire opam universe may be quite large. I’m not entirely sure how good the cache hit would be. Esy implements reliable caching by ensuring transitive dependencies a library is built against, participate in the cache key. So even though two root packages share a dependency, it’s no guarantee you’ll be able to cache the build of that dependency. Still - I find it does in practice greatly reduce new root package build times - usually there will be a few different builds of one package that cause cache hits for a much larger set of packages that depend on it.

1 Like