I don't get the reasoning behind listed the ones below as build deps, i.e. enforcing upstream modules that use `biodeps` as a dep to specify them as dependencies themselves (because build deps are not loaded automagically whenever a module is loaded for runtime use)...
@fgeorgatos: Care to clarify? Is this a way to try and trigger conflicts when another version of these is used by modules who depend on `biodeps`? Because that won't work (`biodeps` build dependencies will be simply ignored when the `biodeps` module is loaded as a dependency for software X).