Howdy Andreas and all,
For 2017b I tried to get ahead of the curve and submit
easyconfigs for the latest version of everything I could.
I maintain a list here of 2017b versions I should use.
I think it would be great if we could have a "definitive"
list of versions each time we start a new
Dear Kenneth,
thanks for the explanation!
Kenneth Hoste writes:
Dear Andres,
We've been keeping a close (automated) eye on which dependencies
are
used in recent common toolchains (foss* & intel*, since 2018a)
in that
respect: we have a test that verifies that there's only a single
Dear Andres,
We've been keeping a close (automated) eye on which dependencies are
used in recent common toolchains (foss* & intel*, since 2018a) in that
respect: we have a test that verifies that there's only a single
"variant" (version + versionsuffix) of a software package used as a
Hey,
I just noticed that library versions are not necessarily used
consistently within one toolchain. For example, in foss-2018b,
there's both Bison-3.0.4 and Bison-3.0.5:
$ grep Bison */*/*.eb | grep foss-2018b
b/bioawk/bioawk-1.0-foss-2018b.eb:builddependencies =
[('Bison',
4 matches
Mail list logo
