Apologies for the delayed reply to this suggestion. I'm currently reworking the opam2-based images and may actually remove the point releases entirely from the tag name in the new images. The reasoning is that we only ever test the latest point release of a given major release.
In the new scheme, that would lead to multiarch images being available for: ocaml/opam2:alpine-3.6-ocaml (with all major releases of OCaml available in one switch) and ocaml/opam2:alpine-3.6-ocaml-4.06 (with all variants of 4.06.0 available in that switch, including flambda/unsafe-safe-string) This leads to slightly bigger images, but will be maintainable in the longer term. Unfortunately we can't build every variant on the opam1 containers due to the combinatorial explosion taking up far too much storage. regards Anil > On 5 Oct 2017, at 08:13, Teoh Han Hui <teohhan...@gmail.com> wrote: > > In addition to tags like: > ocaml/opam:alpine_ocaml-4.04.2 > > There should also be: > ocaml/opam:alpine_ocaml-4.04 > > So that the user can be sure that the latest 4.04 release is always used. > > Of course it'd also be great to have tags for flambda builds. > > So in addition to tags like: > ocaml/opam:alpine_ocaml-4.04.2_flambda > > There should also be: > ocaml/opam:alpine_ocaml-4.04_flambda > > Taking into account all the other possible combinations, we'll also have e.g.: > ocaml/opam:alpine-3.6_ocaml-4.04 > ocaml/opam:alpine-3.6_ocaml-4.04_flambda > _______________________________________________ > opam-devel mailing list > opam-devel@lists.ocaml.org > http://lists.ocaml.org/listinfo/opam-devel
_______________________________________________ opam-devel mailing list opam-devel@lists.ocaml.org http://lists.ocaml.org/listinfo/opam-devel
