For easyconfig files specified on the command line, we don't check
anything, to give people the freedom to name their easyconfig files
"test.eb" or whatever (even the .eb extension isn't required).
Yay!, freedom to shoot ourselves on the foot ;-P. IMO, if the robot can’t pick
it up,
EB ignores the file name and uses the info
inside.
e.g. I could have a file named foo.eb with
the contents:
name = 'foobar'
version = 'barfoo'
toolchain = {'name': 'ABC', 'version': '123'}
And it would generate foobar/barfoo-ABC-123
regardless off the foo.eb filename.
jack
On 03/28/2017
Hello,
I accidently did a build and I noticed easybuild went ahead with the build when
I didn't have foss-2016a in the system but the file name was set that way but
the toolchain name was set to foss-2016.03 which is my custom toolchain. I
suspected that eb would check filename to make sure it
3 matches
Mail list logo
