David Cantrell schrieb:
If you code relies directly on a particular module, then you should list it as a pre-requisite. If, for example, you require Foo and Bar, and Foo requires Bar and Baz, then you should list Foo and Bar. While listing Foo as a pre-req will *currently* also make sure that Bar is installed, Foo may change its pre-reqs in the future.
Thanks - this both extends and confirms my understanding. In the particular module I use SUPER.pm to segregate developer- and user-tests. (if this sounds familiar to you: It is Hack #62). SUPER.pm requires Sub::Identify. The particular module tested, does *not* need Sub::Identify itself. Some tests still fail - even if I copy (not move) anything from configure_requires to build_requires (which may be irrelevant anyway - if I understand the post from David G. right) The only workaround I found: Adding Sub::Identify together with SUPER.pm to build_requires. Does anyone know about a solution? Thanks, Ingo
