Am 26.06.2015 um 13:49 schrieb Aldo Calpini:
On 20/06/15 12:52, K. Wittrock wrote:
set PERL5LIB=lib
prove xt
set PERL5LIB=
you can get rid of the silly PERL5LIB stuff with:
prove --lib xt
Thank you.
also, be aware that testing the not-yet-built lib folder isn't going to
work for XS modul
Am 25.06.2015 um 19:25 schrieb John M Gamble:
On 6/20/2015 5:52 AM, K. Wittrock wrote:
Just to supplement Karen's response:
[.]
I add the following lines to MANIFEST.SKIP to prevent xt/ from
reaching the tarball:
# Avoid author tests dir.
^xt/
The problem I have with that is that s
On 6/29/2015 7:01 AM, David Cantrell wrote:
On Thu, Jun 25, 2015 at 12:25:28PM -0500, John M Gamble wrote:
The problem I have with that is that since the author tests are there
for their usefulness, it
makes sense to keep them in the distribution for the next author (be it
a hand-off or a fork)
On Thu, Jun 25, 2015 at 12:25:28PM -0500, John M Gamble wrote:
> The problem I have with that is that since the author tests are there
> for their usefulness, it
> makes sense to keep them in the distribution for the next author (be it
> a hand-off or a fork).
>
> Sure, keep the author tests se
++
On Fri, Jun 26, 2015 at 7:49 AM, Aldo Calpini wrote:
> On 20/06/15 12:52, K. Wittrock wrote:
>
>> set PERL5LIB=lib
>> prove xt
>> set PERL5LIB=
>>
>
> you can get rid of the silly PERL5LIB stuff with:
>
> prove --lib xt
>
> also, be aware that testing the not-yet-built lib folder isn't going
On 20/06/15 12:52, K. Wittrock wrote:
set PERL5LIB=lib
prove xt
set PERL5LIB=
you can get rid of the silly PERL5LIB stuff with:
prove --lib xt
also, be aware that testing the not-yet-built lib folder isn't going to
work for XS modules, or any module which does something more than just
copyi
On 6/20/2015 5:52 AM, K. Wittrock wrote:
Just to supplement Karen's response:
Am 18.06.2015 um 18:58 schrieb Vincent Lequertier:
Since I'm fairly new to the task of maintening modules, and that I'm
unable to find any doc about it, is moving a test file from /t to /xt
make the test secondary? A
Thank you for your answer :-) Using author tests could also solve my
problem. Your commands work for a Build.pl based distribution.
I'm planning to find a proper way to generate a DZT-Sample-0.001.tar.gz
file dynamically.
Le 20/06/2015 12:52, K. Wittrock a écrit :
> Just to supplement Karen's res
Just to supplement Karen's response:
Am 18.06.2015 um 18:58 schrieb Vincent Lequertier:
Since I'm fairly new to the task of maintening modules, and that I'm
unable to find any doc about it, is moving a test file from /t to /xt
make the test secondary? Any advice?
I add the following lines to
I added the file in the distribution, as a workaround. Thank you very
much for your help Karen ;-)
Le 18/06/2015 19:14, Karen Etheridge a écrit :
> For that test, it sounds like the missing file should be added to
> the corpus/dist/ directory so the tests can use it.
>
> Alternatively, the tests
For that test, it sounds like the missing file should be added to the
corpus/dist/ directory so the tests can use it.
Alternatively, the tests should generate that file itself (just alter the
tests to include all the Dist::Zilla plugins needed for a regular build, so
it can generate the tarball th
Hi list,
I'm maintaing this module https://metacpan.org/pod/Dist::Zilla::Plugin::RPM
and I have this issue https://rt.cpan.org/Ticket/Display.html?id=105307
...which I'm able to reproduce. The issue can be fixed by including
DZT-Sample-0.001.tar.gz to the distribution or by excluding
t/02release
12 matches
Mail list logo
