In the future it may be worth thinking about format versioning, so that next-version server can apply an adaptation layer when talking to previous-version clients.
On Wed, Jan 15, 2014 at 10:27 AM, Louis Gesbert <[email protected]> wrote: > On Tuesday 14 January 2014 17:34:55 Anil Madhavapeddy wrote: >> On 14 Jan 2014, at 17:11, Louis Gesbert <[email protected]> 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. > > Any opinions on this ? The problem still exists even if we shift that after > release. > > Cheers, > Louis > _______________________________________________ > Platform mailing list > [email protected] > http://lists.ocaml.org/listinfo/platform _______________________________________________ Platform mailing list [email protected] http://lists.ocaml.org/listinfo/platform
