On Aug 3, 2006, at 9:01 PM, David Golden wrote:
Dmitri Tikhonov wrote:
I have a test suite for my distribution (RT-Client-REST) that
requires
some modules that the module itself does not require
(Test::Exception,
for example). Since it is not listed as a dependency, some people's
tests fail[1,2].
Question: is it a good idea to put Test::Exception in as a
dependency?
My problem with this is that the module itself, once installed, does
not use Test::Exception, so it is not really a dependency. On the
other
hand, I want all tests to run (most of them test exceptions), so I do
not want to 'skip' any tests.
Is it a good idea? "It depends."
There's an argument to be made for not forcing people to download
extra modules. But most of the "build_requires" type approaches
don't seem to work well in practice.
My intention when I added 'build_requires' to Module::Build was not
to let people avoid downloading & building those dependencies, but
rather to indicate that there was no runtime dependency, so if people
are tracking their modules using RPMs or Debs or whatever, they could
know what really depended on what.
-Ken
