"TAPlug"s for TAP::Harness
nick at ccl4.org
Thu Jun 11 12:42:33 GMT 2009
On Wed, Jun 10, 2009 at 03:57:02PM -0400, David Golden wrote:
> The problem continues to be that "everyone" would need to have
> TAP::Harness and an upgraded toolchain that is TAP::Harness aware. So
> until configure_requires is widespread, I think you're stuck
> supporting the legacy interface.
Why? This is "test_requires", isn't it, rather than "configure_requires",
so surely a regular dependency on TAP::Harness $whatever in a Makefile.PL
would be good enough?
> The related problem is that you have two types of users:
> (a) developers, who may or may not do something custom with the
> harness in the build tools of a distribution
> (b) end-users, who may or may not want some custom harness behavior
> and likely do not want to mess with the build-tools in an distribution
Which actually isn't anything that configure_requires will solve, is it?
The problem there is that prerequisites needed for testing, however specified,
need to be installed, and Perl 5 doesn't support the installation of multiple
versions in parallel, hence there's no way have another module available only
on a temporary basis for the duration of testing.
More information about the tapx-dev