Bootstripping
Ovid
publiustemp-tapx at yahoo.com
Thu Aug 21 15:09:41 UTC 2008
I like to think of "bootstripping" as "bootstrapping when you shouldn't". I've noticed that we are now testing against ourself. Thus, when Andy's change to not strip extensions kicked in, "./Build test" and "make test" generates things like:
t/harness.t ........... ok
Rather than:
t/harness ............. ok
But prove -rl t/ works as expected. I see comments in the Makefile.PL which explain that if we don't test against ourself, we end up loading a confused mixture of installed and new modules, but I don't feel that comfortable having Test::Harness self testing (I don't if an older version tests a "to be installed" version, of course).
Is there no way around this or am I being overly paranoid?
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
More information about the tapx-dev
mailing list