Hi Kennth, all, sorry for the delay in replying -- I'm task-switching with too many tasks in my run queue...
On 3 June 2014 22:18, Kenneth Hoste <[email protected]> wrote: > > On 03/06/14 21:58, Riccardo Murri wrote: >> >> How about using a "year.month" scheme, e.g., goolf-14.06 would be the >> GCC+OpenMPI+... that are current during June 2014? > > That sounds reasonable, but might introduce artificial limits too, I think. > > Toolchain elements aren't always updated; sometimes we need to go back to > older versions for testing/benchmarking/compatibility reasons. > > How would you version a toolchain that combines GCC v4.9 (new) and OpenMPI > v1.6 (old) with this scheme? How about adding a letter (or a longer alphanumeric tag) at the end to distinguish between "series" of toolchain releases? One series should be the "current" one with the newest releases in the tagged year/month; another series could features patched or compatibility versions of some packages. Examples: * 14.05 : current upstream GCC+OpenMPI as of May 2014 * 14.05a : GCC current; older OpenMPI for compatibility * 14.05b : GCC+OpenMPI current; patched OpenBLAS for whatever reason It would probably be next to impossible to come up with a set of tags that is both concise, expressive (= makes sense to users), and agreed upon by many HPC admins. However, we might not need that: a simple registry (e.g., wiki page) of tags should suffice, and sources would depend on the toolchain's major version not the series, anyway. I understand this is a thorny topic that has probably been discussed many times over. Please excuse me if I just re-hash suggestions that have already been made and discussed. Ciao, R -- Riccardo Murri http://www.gc3.uzh.ch/people/rm Grid Computing Competence Centre University of Zurich Winterthurerstrasse 190, CH-8057 Zürich (Switzerland) Tel: +41 44 635 4222 Fax: +41 44 635 6888
