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 toolchain.
Of course that's a non-trivial task, but I would start
with the versions provided in the latest version of
Ubuntu and/or Fedora at the time as a guide.
That way as we introduce new toolchains we can
keep pace with the latest and most popular distributions.
For 2018* I've just been using what EB provides
(no version restrictions) so they are a mess of different
versions.
Jack Perdue
Lead Systems Administrator
High Performance Research Computing
TAMU Division of Research
[email protected] http://hprc.tamu.edu
HPRC Helpdesk: [email protected]
On 11/22/18 11:06 AM, Andreas Hilboll wrote:
Dear Kenneth,
thanks for the explanation!
Kenneth Hoste <[email protected]> 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
"variant" (version + versionsuffix) of a software package used as a
runtime dependency (with some exceptions, e.g. Python 2.x & 3.x).
We're not doing this for build dependencies though, which is why there
are two versions of Bison used in easyconfigs that use a 2018b
toolchain.
Ah, okay, I didn't think about that distinction. And I understand
that for build dependencies, one might want the extra freedom of not
enforcing this policy.
For Bison, it's a bit silly, but we have seen situations where at some
point a newer CMake was required than the one that was already being
used...
The main reason for the "one dep variant" policy is to avoid version
conflicts as much as possible between easyconfigs using the same
toolchain. We learned the hard way that you run into hard to fix
problems if you don't maintain a policy like this...
Any particular reason for your question?
No, not really. I just noticed that for one install (I'm updating
Octave to 4.4.1), eb wants to build both Bison versions, which I found
silly, so I got curious. But your explanation makes perfect sense.
Cheers,
Andreas
