Hi Stuart,
On 02/03/15 20:02, Stuart Barkley wrote:
On Mon, 2 Mar 2015 at 12:53 -0000, Kenneth Hoste wrote:
What you are stumbling over is that --robot-paths (in combination
with any paths that may be specified via --robot) are not being
considered for easyconfig files that are specified on the command
line (by name-only/relative path), while the readily provided
easyconfig files *are* being consider.
To clarify, with "eb foo.eb", if there's no file named 'foo.eb' in
the current working directory, eb will go and see whether there's an
easyconfig file with that name in the collection of readily avaiable
easyconfigs that are part of the EasyBuild installation, but it will
not look for 'foo.eb' in the directories listed in --robot-paths (or
--robot).
Did I get that right?
Yes, I think this is a good rewording of the problem I'm seeing.
After briefly discussing this during the EasyBuild conf call yesterday
and basically agreeing with the other 'regulars' that this change makes
a lot of sense,
it was implemented and merged into the develop branch of the EasyBuild
framework today, see
https://github.com/hpcugent/easybuild-framework/pull/1201.
The example in the PR description should help in making clear what
changed exactly.
This will be part of EasyBuild v2.0 which will be released in the next
couple of days.
regards,
Kenneth
