[opam-devel] [ocaml-platform] OPAM 1.1.1 RC

Anil Madhavapeddy anil at recoil.org
Wed Jan 15 10:03:29 GMT 2014

On 15 Jan 2014, at 09:27, Louis Gesbert <louis.gesbert at ocamlpro.com> wrote:

> On Tuesday 14 January 2014 17:34:55 Anil Madhavapeddy wrote:
>> On 14 Jan 2014, at 17:11, Louis Gesbert <louis.gesbert at ocamlpro.com> wrote:
>>> Last addition was the possibility for packagers to specify `archive: ["upstream-url" "mirror1" "mirror2"]` in the url files, so that we have a way to circumvent downtime of package hosting servers -- like recently happened for camlcity with dire consequences for new OPAM installations (ocamlfind could not be installed). We are working on a more general mirroring solution for the next release.
>> I don't think this should be included in 1.1.1, since it changes the repository format.  For instance, is there a clear backwards compatibility story for 1.1.0 clients that connect to a repository that includes multiple archives?
> Indeed, that would break (quite badly) -- Thomas thought that the url file already supported (unused) archive lists, but that must have been removed at some point.
> If it's very important to have this now, I can modify the patch so that it only changes the repo in a 1.1.0-compatible way, by adding a `mirror` field instead of changing the current type of the `archive` and similar fields. I tend to think that the smoothness of upgrade may be worth the slightly less clear resulting file format.

It's not critical to have it right now.  Unplanned outages happen, and this one might have happened right after the 1.1.1 release and the world won't end.  Let's pull it and implement the feature more thoroughly in 1.2.0 rather than cram it into a point release.

> Any opinions on this ? The problem still exists even if we shift that after release.

Not necessarily.  We could bump the repo version in 1.2.0 and think about a compatibility shim for 1.1.0 (via opam-admin rewrites).


> Cheers,
> Louis

More information about the opam-devel mailing list