Is there a good way to see a dependency tree with easybuild (I'm now
running 2.0.0)? I'm trying to reconcile different dependency
requirements for my large build and am finding it difficult to
determine what packages are requiring other packages.
Currently I am using 'eb --dry-run --robot' to get a complete list of
packages for a potential build, but I cant seem to figure out how to
determine which packages are causing certain other things to be
required.
Up until now, I've just been doing builds and when things die, fix
that problem and restart the build. This works after a fashion, but
takes a long time when there are multiple issues. Also, once I've
completed a build I need to go back are rebuild everything again in
case one of the later changes impacted an earlier build.
After a build is complete, I can do some grepping of the .eb files in
ebfiles_repo, but even this gets awkward.
Part of the cause of this issue is that I'm creating a couple of .eb
files with the set of software I want to install (similar to the
HPCBIOS files). Currently, it appears that everything in a single .eb
file needs to use the same library versions and some of the packages
use different library versions (zlib, libpng, boost, cmake).
Another useful option would be a --keep-going option to have easybuild
continue on with other packages even if one fails. I would like to
start a build before going home and have easybuild do as much as
possible.
Thanks,
Stuart
--
I've never been lost; I was once bewildered for three days, but never lost!
-- Daniel Boone
