Hi Fotis et al., On 05 Jun 2013, at 11:21, Fotis Georgatos wrote:
> > Hi Jens et al, > > On Jun 5, 2013, at 9:40 AM, Jens Timmerman wrote: >> What exactly do you want to know? > > I can expand on this question: > * If you care about the build graph, the --dep-graph provides the answer > * If you instead want to know what is already installed and what not, > that is a different question and often arises in operations > > (eg. how many of the ictce/5.3.0 easyconfigs are already delivered?) > > Think of your package manager reporting on a "Bioinfo-tools" metapackage, > how many of its deps are already satisfied and how many need to be built. > > I think this could be called -n "dry-run" , ala rsync style, no? > (but perhaps you are already doing that in some other manner) OK, if I get this correctly, you'd like to see some command line option that simply prints which modules are going to be built? E.g.: eb GCC-4.6.3.eb OpenMPI-1.6.4-GCC-4.6.3.eb test-gompi.eb --dry-run GCC/4.6.3 OpenMPI/1.6.4-GCC-4.6.3 gompi/1.1.0 If this matches what you need, please open an issue for this (in framework), it shouldn't be too hard to add support for that. K.
