don't specify shell to use for modulecmd commands, it breaks stuff (" Usage is '/usr/bin/modulecmd shellname' ")

i.e. use /bin/bash as shell for root script (refs #180)

specify /bin/bash as executable for running system commands (required for Ubuntu), check if environment-modules is installed (refs #180)

specify "/bin/bash" as executable for running system commands, make sure that environment-modules dependency is installed

bunch of fixes to enable robot to perform quick demo (i.e. build HPL with goalf toolkit, from scratch) (refs #249)

also prepare for toolkit itself, if there a preparation function available

extend MODULEPATH with <installPath>/modules/all to make sure that EasyBuild is able to resolve it's dependencies (refs #250)

extend subdir paths in which robot tries to find specification files, check if expected module is obtained when processing a .eb spec file match, make sure that resolveDependencies doesn't get stuck in an infinite loop (by adding a loop counter and a max loop count)

add sourceURLs to all example .eb spec files, and make sure naming scheme is OK for robot to find the files

try and create build/install/source paths if they don't exist already (refs #217)

try and create build/install/source paths if they don't exist already (refs #217)

give command line config file preference over enviroment variable EASYBUILDCONFIG, minor tweaks to default config and error reporting (refs #217)

give command line config file preference over enviroment variable EASYBUILDCONFIG, minor tweaks to default config and error reporting