After a little hiatus I'm back working using easybuild to build
software for our system.

One issue which was confusing me for a while was some unexpected
choices for the *.eb files under different conditions.

I was making modifications to some of the standard .eb files by
putting modified copies in my working directory.  Changes included
adding the --with-sge option in the OpenMPI .eb file or adjusting
software versions (some older distfiles are not longer available for
download).  I also was creating a meta .eb file to reference other
packages.

I was getting inconsistencies between doing explicit eb commands and
using the --robot option.  Eventually I found out that my local
changes were not being seen with --robot and that I needed to add a
--robot-paths option in my configuration file.

Later I had enough .eb files that I decided to move them into a
easyconfig subdirectory (adjusting the --robot-paths option).  At that
time I found that just doing 'eb xxx.eb' was not finding the files in
my private easyconfig directory but instead again using the eb-1.6.1
distributed versions.  This is still a little awkward in that I need
to include the directory when building a package with local
modifications.

My suggestion is that --robot-path (perhaps renamed) should apply to
.eb files given on the command line in addition to those searched for
with --robot.

Stuart
-- 
I've never been lost; I was once bewildered for three days, but never lost!
                                        --  Daniel Boone

Reply via email to