If you use Module::Install, there's a separate option called "build_requires" that should do what you want. People installing from source via CPAN will have to download the build_requires, because they're building the packages, but users of pre-compiled (and tested) binary distributions won't be asked to install the modules that your test depends on.
If you're not using Module::Install, though, I would include Test::Exception as a regular dependency anyway. You'll get better feedback from the CPAN testers that way, and that's probably more important than worrying about whether or not someone needs to install T::E. It's a pretty standard module; they'll need it sooner or later :) Regards, Jonathan Rockway Dmitri Tikhonov wrote: > > Dear fellow Perl module authors: > > 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. > > Thanks for your input, > > - Dmitri. > > 1. http://www.nntp.perl.org/group/perl.cpan.testers/340611 > 2. http://www.nntp.perl.org/group/perl.cpan.testers/340620 >
signature.asc
Description: OpenPGP digital signature
