Skip Menu |

This queue is for tickets about the Pod-Constants CPAN distribution.

Report information
The Basics
Id: 61780
Status: resolved
Priority: 0/
Queue: Pod-Constants

People
Owner: Nobody in particular
Requestors: mschwern [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Normal
Broken in: 0.16
Fixed in: 0.17



Subject: Do not rely on MM->new
It was pointed out to me that the Makefile.PL is making direct calls to MM->new. Please do not rely on that or poking at any other undocumented method of MakeMaker. It will break. Your Makefile.PL is doing some very, very strange stuff to do what MakeMaker already does. What's going on?
On 2010-09-29 18:49:03, MSCHWERN wrote: Show quoted text
> It was pointed out to me that the Makefile.PL is making direct calls to > MM->new. Please do not rely on that or poking at any other undocumented > method of MakeMaker. It will break. > > Your Makefile.PL is doing some very, very strange stuff to do what > MakeMaker already does. What's going on?
Is this the reason why the module does not build anymore since perl 5.13.5? See http://matrix.cpantesters.org/?dist=Pod-Constants&maxver= Regards, Slaven
On 2010-09-29 18:49:03, MSCHWERN wrote: Show quoted text
> It was pointed out to me that the Makefile.PL is making direct calls to > MM->new. Please do not rely on that or poking at any other undocumented > method of MakeMaker. It will break. > > Your Makefile.PL is doing some very, very strange stuff to do what > MakeMaker already does. What's going on?
It seems that the Makefile.PL tries to get the value of FULLPERL, store it into a temporary file, and use this value in test scripts. In t/01-constants.t the value is read, and used as a possible perl path together with $^X and $Config{perlpath}. But: I never heard that $^X is not good enough, so this construct is probably unnecessary. Additionally, in newest EUMM versions the FULLPERL value is quoted, so it would never pass the -x check in https://metacpan.org/source/SAMV/Pod-Constants-0.16/t/01-constants.t#L56 .