Because a dependency specification like `('OpenMPI`, `1.6.4`, '', ('GCC', '4.7.2'))` only contains information about `name`, `version`, `versionsuffix` and `toolchain`, we can only guarantee to provide that information (currently, will be fixed in #687). The `det_full_module_name` function is also called for all dependencies listed in an easyconfig, to figure out whether the required modules are available or not.

What other errors may occur by using non-available easyconfig parameters?
Of course, if there are bugs in the module naming scheme implementation, `eb` will crash and burn. I guess we could/should be more robust there, but to only catch the use of easyconfig parameters that are not available, catching `KeyError` is sufficient, no? I may be missing something...