On May 20, 2008, at 21:20, Eric Wilhelm wrote:
# from David Golden on Tuesday 20 May 2008:
On Tue, May 20, 2008 at 11:03 PM, Adam Kennedy
Personally, I'd like to see configure_requires: finalised first
before we start dealing with test_requires, so that we have the
option of solutions that themselves leverage configure_requires:
+1
Gee, I thought it was finalized. I've added it to all of my modules
and it's included in my META.yml thanks to the version of
Module::Build that ships with Perl 5.10.
That sounds reasonable. In fact, I would like to see something that
allows META.yml to require compatibility with a given version of the
META.yml spec.
Not a bad idea.
Taking 'test_requires:' as an example, note that any older installer
will not be looking at that key and the tests will fail, so one would
have to list those prereqs in 'requires:' for backward compatibility,
but then that muddles the desired distinction.
Yeah, that would suck.
Personally, I wanted it, though, so that in a corporate environment
OPS could install a module using ./Build instal (no CPAN) without a
failure because test modules aren't installed.
Best,
David
