<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Apologies for the delayed reply to this suggestion.  <div class=""><br class=""></div><div class="">I'm currently reworking the opam2-based images and may actually remove</div><div class="">the point releases entirely from the tag name in the new images.  The</div><div class="">reasoning is that we only ever test the latest point release of a given </div><div class="">major release.</div><div class=""><br class=""></div><div class="">In the new scheme, that would lead to multiarch images being available</div><div class="">for:</div><div class=""><br class=""></div><div class="">ocaml/opam2:alpine-3.6-ocaml</div><div class="">(with all major releases of OCaml available in one switch)</div><div class=""><br class=""></div><div class="">and</div><div class=""><br class=""></div><div class="">ocaml/opam2:alpine-3.6-ocaml-4.06</div><div class="">(with all variants of 4.06.0 available in that switch, including flambda/unsafe-safe-string)</div><div class=""><br class=""></div><div class="">This leads to slightly bigger images, but will be maintainable in the longer</div><div class="">term.  Unfortunately we can't build every variant on the opam1 containers</div><div class="">due to the combinatorial explosion taking up far too much storage.</div><div class=""><br class=""></div><div class="">regards</div><div class="">Anil</div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On 5 Oct 2017, at 08:13, Teoh Han Hui <<a href="mailto:teohhanhui@gmail.com" class="">teohhanhui@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">In addition to tags like:<div dir="auto" class="">ocaml/opam:alpine_ocaml-4.04.2</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">There should also be:</div><div dir="auto" class="">ocaml/opam:alpine_ocaml-4.04</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">So that the user can be sure that the latest 4.04 release is always used.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Of course it'd also be great to have tags for flambda builds.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">So in addition to tags like:</div><div dir="auto" class="">ocaml/opam:alpine_ocaml-4.04.2_flambda<br class=""></div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">There should also be:</div><div dir="auto" class=""><span style="font-family:sans-serif" class="">ocaml/opam:alpine_ocaml-4.04_flambda</span><br class=""></div><div dir="auto" class=""><span style="font-family:sans-serif" class=""><br class=""></span></div><div dir="auto" class=""><font face="sans-serif" class="">Taking into account all the other possible combinations, we'll also have e.g.:</font></div><div dir="auto" class=""><span style="font-family:sans-serif" class="">ocaml/opam:alpine-3.6_ocaml-4.04</span><font face="sans-serif" class=""><br class=""></font></div><div dir="auto" class=""><span style="font-family:sans-serif" class="">ocaml/opam:alpine-3.6_ocaml-4.04_flambda</span><font face="sans-serif" class=""><br class=""></font></div></div>
_______________________________________________<br class="">opam-devel mailing list<br class=""><a href="mailto:opam-devel@lists.ocaml.org" class="">opam-devel@lists.ocaml.org</a><br class="">http://lists.ocaml.org/listinfo/opam-devel<br class=""></div></blockquote></div><br class=""></div></body></html>