On Wed, Mar 29, 2017 at 8:37 PM, Dan Collins wrote:
> Huh, I just found another interesting thing. CPAN::Reporter makes no effort
> to report on whether the `install` phase succeeded, but some particularly
> creative dists manage to fail in the `install` phase under
>
> On Wed, 29 Mar 2017 14:37:30 -0400, Dan Collins
> said:
> Huh, I just found another interesting thing. CPAN::Reporter makes no
> effort to report on whether the `install` phase succeeded, but some
> particularly creative dists manage to fail in the `install`
Huh, I just found another interesting thing. CPAN::Reporter makes no effort
to report on whether the `install` phase succeeded, but some particularly
creative dists manage to fail in the `install` phase under
PERL_USE_UNSAFE_INC=0. Look at this example
from GUIDO/libintl-perl-1.26.tar.gz - does
Porters, I heard you wanted some red and yellow...
I have tooling set up that allows me to test/install most of CPAN, saving
the CPAN::Reporter results to file, and compare those stored files between
two different versions of perl. I installed two instances of perl - cpan1
and cpan2 - which are
I've gone and built a naive version of this for my own uses. It doesn't
yet hook into cpanm-reporter but i don't think it'd be hard to do. It's
intending to take a --module or --cpanfile to start from and works its way
through the dependency tree (fetches it all with cpanm --showdeps) and then
Hello Kent,
I didn't know this environment variable, but I understand the concern.
On the other hand, it doesn't seem to be a easy thing to fix:
http://www.nntp.perl.org/group/perl.perl5.porters/2016/11/msg241020.html
https://www.effectiveperlprogramming.com/2017/01/v5-26-removes-dot-from-inc/
On 27 March 2017 at 16:10, Dan Collins wrote:
> I've had a chance to make sure that this test environment isn't horribly
> broken...
Yeah, there's enough broken you sort of need a double-testing system.
Start with =0 , and then upon hitting a failure, retry with =1 ...
I started the process of running a cpan smoke test for this and noticed
that even CPAN::Reporter and YAML::Syck fail under PERL_USE_UNSAFE_INC=0.
I'll start uploading reports and sharing results with the list once I've
had a chance to make sure that this test environment isn't horribly
broken...