# from David Golden
# on Wednesday 02 December 2009 16:37:
>> We can't really draw a line between "core" and "author support" --
>> only between "core" and "not core" (because what was once in "core"
>> is
>
>Sorry. I was imprecise. I was not saying "core" to mean "Perl core".
> Just what is *es
On Wed, Dec 2, 2009 at 6:17 PM, Eric Wilhelm wrote:
> # from David Golden
> # on Wednesday 02 December 2009 14:59:
>
>>Anyway, when that's done, I think I'll have a clearer sense of what in
>>M::B is really "core" and what is "author support". That said,
>>plugins are probably not on my radar in
# from David Golden
# on Wednesday 02 December 2009 14:59:
>Anyway, when that's done, I think I'll have a clearer sense of what in
>M::B is really "core" and what is "author support". That said,
>plugins are probably not on my radar in the next year.
We can't really draw a line between "core" an
On Wed, Dec 2, 2009 at 1:42 PM, Eric Wilhelm wrote:
> This has triggered my semi-biyearly ponderance of plugins. I
> think "tools for authors" should be doable outside of M::B. And/or
> more easily customized than via subclassing, plus more easily shared
> between distributions than via copy+pas
# from David Golden
# on Thursday 26 November 2009 05:10:
>How about this:
>
>(1) We add a "testrelease" action that sets RELEASE_TESTING and calls
>a list of other testing actions
>
>(2) We add a 'testxt' action that runs tests in xt/; this is common
>enough now that we might as well make it easy
On Thu, Nov 26, 2009 at 1:43 AM, Adam Kennedy
wrote:
> Addition to David's reply, the use of xt was suggested as a
> convenience (not as a requirement) that tools may or may not choose to
> use to indicate tests that run during RELEASE_TESTING. They won't
> define tests that MUST be run during REL
Addition to David's reply, the use of xt was suggested as a
convenience (not as a requirement) that tools may or may not choose to
use to indicate tests that run during RELEASE_TESTING. They won't
define tests that MUST be run during RELEASE_TESTING.
Adam K
2009/11/25 Dave Rolsky :
> It seems lik
On Tue, Nov 24, 2009 at 1:23 PM, Dave Rolsky wrote:
> It seems like using an xt dir and an AUTHOR_TESTING env var is the emerging
> standard for managing author-only tests.
>
> Can we change Module::Build to include the xt dir if this env var is set?
The Oslo Consensus [1] agreed to use RELEASE_T
It seems like using an xt dir and an AUTHOR_TESTING env var is the
emerging standard for managing author-only tests.
Can we change Module::Build to include the xt dir if this env var is set?
-dave
/*
http://VegGuide.org
