So the good news is that I was able to convince the author to let me include my dependancies in the test library. So I'll switch to Test::More.
Thanks for the help. On 4/12/05, Michael G Schwern <[EMAIL PROTECTED]> wrote: > On Tue, Apr 12, 2005 at 04:15:01PM -0500, Walter Goulet wrote: > > I think the suggestion to use Test::Legacy was based on the statement > > 'backwards compatibility reasons' require me to use Test.pm. I should > > have been clearer in my explanation; the module author is not > > permitting me to use any additional modules that aren't included in > > perl 5.6.0 to test his module. Therefore, I am restricted to only > > using Test.pm for testing the module. > > Is there a reason for this odd policy? The only thing I can think of is > to avoid users having to download and install additional dependencies but > the t/lib trick takes care of that. > > Test::Builder/More/Simple are tested back to 5.004_05 so there's no > compatibility issue. > > If you want to go all the way you can try out Module::Install and PAR to > completely break the dependency problem. > > > > If only I could convince the author to let me bundle additional test > > modules with his distribution... > > If logic isn't working you might just want to go with the "everybody's doing > it" argument. > FWIW here's some important projects which do the t/lib trick. > > ExtUtils::MakeMaker > http://search.cpan.org/src/MSCHWERN/ExtUtils-MakeMaker-6.27/t/lib/ > > Test::Harness > http://search.cpan.org/src/PETDANCE/Test-Harness-2.47_03/t/lib/ > > mod_perl > http://perl.apache.org/dist/mod_perl-2.0-current/t/lib/ > > Parrot > https://svn.perl.org/parrot/trunk/lib/ > > xmlstream > http://www.jabberstudio.org/cgi-bin/viewcvs.cgi/cvs/xmlstream/t/lib/ > > darcs > http://abridgegame.org/cgi-bin/darcs.cgi/darcs/tests/lib/perl/?c=browse > >