The upstream module in question has dual-build, so its not a show-stopper, however, our eclass situation is such that gentoo will:
-
In the presence of a
Build.PL
file, always usedModule::Build
style invocation, regardless of truth. -
In the scenario where
Build.PL
is NotModule::Build
, erroneously complain about a dependency onModule::Build
, which is not necessary -
Also entirely fail to QA check on the appropriate dependency when Build.PL requires some other things.
Essentially, the QA check we have in place is a bit wonky, and the mechanism that triggers it is wonky and unreliable too.