Adam Kennedy wrote:
> I'm not suggesting we test against the post-make code, but if we keep
> everything, we can be fairly certain we still have any data files or
> other things that are needed to support the testing.
>
> Now we rerun the test suite, but without including blib.
>
> And you get a
Adam Kennedy wrote:
>> Hmm, that would waste a lot of disk. Maybe we could cache the
>> tarballs somewhere. Maybe on the network or even Amazon S3. Some
>> sort of big repository of modules. We can call it the Network of
>> Archived Postinstall Crap, NAPC for short!
>
> This same argument appl
On 13 Sep 2006, at 19:28, Michael G Schwern wrote:
Adrian Howard wrote:
On 13 Sep 2006, at 05:37, Michael G Schwern wrote:
[snip]
(For the sarcasm impaired, if you're just going to store the whole
post-install source tarball you might as well just grab it from CPAN
again)
[snip]
Isn't the
Adrian Howard wrote:
>
> On 13 Sep 2006, at 05:37, Michael G Schwern wrote:
> [snip]
>> (For the sarcasm impaired, if you're just going to store the whole
>> post-install source tarball you might as well just grab it from CPAN
>> again)
> [snip]
>
> Isn't the post-install source tree potentially
On 13 Sep 2006, at 05:37, Michael G Schwern wrote:
[snip]
(For the sarcasm impaired, if you're just going to store the whole
post-install source tarball you might as well just grab it from
CPAN again)
[snip]
Isn't the post-install source tree potentially different in useful
ways from the
On Tuesday 12 September 2006 21:37, Michael G Schwern wrote:
> (For the sarcasm impaired, if you're just going to store the whole
> post-install source tarball you might as well just grab it from CPAN again)
I believe you meant to say BackPAN.
-- c
Adam Kennedy wrote:
> Frankly, I think anything you might write to try and pick and choose
> what to install is going to have problems.
>
> Since we're wasting... ermm... using all this extra disk space for tests
> anyway, why not just do the lot.
>
> Take the entire distribution post-make and ju
On Sep 12, 2006, at 8:20 PM, Adam Kennedy wrote:
Frankly, I think anything you might write to try and pick and
choose what to install is going to have problems.
Since we're wasting... ermm... using all this extra disk space for
tests anyway, why not just do the lot.
Take the entire distri
Frankly, I think anything you might write to try and pick and choose
what to install is going to have problems.
Since we're wasting... ermm... using all this extra disk space for tests
anyway, why not just do the lot.
Take the entire distribution post-make and just tarball that up and save
i
On Mon, 11 Sep 2006, David Golden wrote:
* test.pl vs t/*.t
* Custom Makefile.PL or Build.PL that affects test runs
* build_requires modules bundled in inc/
And don't forget that some tests may include tests data that is needed to
run the tests. If we're lucky, it's under t/
-dave
/*=
- Original Message
From: Ken Williams
> Yes, I've been thinking about this for a long time. In fact, in the
> most recent M::B beta I made some steps toward it, by adding a
> 'retest' action that's just like 'test' except that it doesn't look
> in blib/, just in @INC. Functionally that
On Sep 11, 2006, at 7:08 PM, Randy W. Sims wrote:
Ovid wrote:
Last week I was at a testing conference with Acme and he came up
with the idea of installing tests. He looked into hacking
Module::Build and ExtUtils::MakeMaker. He also considered hacking
CPAN.pm and CPANPLUS.pm. While I
Ovid wrote:
Last week I was at a testing conference with Acme and he came up with the idea
of installing tests. He looked into hacking Module::Build and
ExtUtils::MakeMaker. He also considered hacking CPAN.pm and CPANPLUS.pm.
While I don't know if he plans to continue working on this
On Sep 11, 2006, at 8:02 AM, Ovid wrote:
Last week I was at a testing conference with Acme and he came up
with the idea of installing tests. He looked into hacking
Module::Build and ExtUtils::MakeMaker. He also considered hacking
CPAN.pm and CPANPLUS.pm. While I don't know if he
Ovid wrote:
I love this idea, but here are some issues that we spotted:
1. How does one install tests for modules already installed?
2. If you install a module with already failing tests, you need to track what
the failures are so you can note different failures when you run the test suite
i
On 11 Sep 2006, at 14:02, Ovid wrote:
Last week I was at a testing conference with Acme and he came up
with the idea of installing tests. He looked into hacking
Module::Build and ExtUtils::MakeMaker. He also considered hacking
CPAN.pm and CPANPLUS.pm. While I don't know if he pla
Last week I was at a testing conference with Acme and he came up with the idea
of installing tests. He looked into hacking Module::Build and
ExtUtils::MakeMaker. He also considered hacking CPAN.pm and CPANPLUS.pm.
While I don't know if he plans to continue working on this idea, he sa
17 matches
Mail list logo
