> The common solution is to NOT add "author-only" tests to TEST_REQUIRES,
but instead to modify your "skip_all" as follows:
>
> unless( ( $ENV{'RELEASE_TESTING'} || $ENV{'AUTHOR_TESTING'} ) && eval
'use Test::POD; 1;' ) {
>plan skip_all => 'These tests are for authors only.';
>exit 0;
> }
The "right" thing to do is to put it in xt/ without any skips and make
sure the release machinery is scripted to make sure xt tests pass before
release.
David
On Mon, Feb 29, 2016 at 3:14 PM, Olivier Mengué
wrote:
> > The common solution is to NOT add "author-only" tests to TEST_REQUIRES,
> bu
Hi
Kent Fredric has proposed 2 alternate patches to my most recent
Makefile.PL for Tree::DAG_Node (V 1.28).
The point is to completely remove the need for an end-user of this - and
of other - modules to have Test::Pod installed.
It's not clear from these patches, but the upper part of both
I see nothing unsafe about either patch, so long as the meta-spec is
specified as version 2. Can you clarify your concerns?
Perhaps reading the section in prerequisite phases in the meta spec might
clarify things a bit:
https://metacpan.org/pod/CPAN::Meta::Spec#PREREQUISITES
(PS. I found the disc
Hi Karen
On 01/03/16 13:29, Karen Etheridge wrote:
I see nothing unsafe about either patch, so long as the meta-spec is
specified as version 2. Can you clarify your concerns?
He did not specify. I assume he'd never seen it in the wild, as I had
not. Likewise I had not read that doc thoroughly
