Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-28 Thread Ron Savage 

Hi Karen

On 29/09/16 09:14, Karen Etheridge wrote:

If those prereqs are needed at runtime, they belong in PREREQ_PM.
BUILD_REQUIRES is only for things needed at the "make" or "./Build" step.


Thanx.

--
Ron Savage - savage.net.au

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-28 Thread Karen Etheridge 
If those prereqs are needed at runtime, they belong in PREREQ_PM.
BUILD_REQUIRES is only for things needed at the "make" or "./Build" step.

On Wed, Sep 28, 2016 at 3:39 PM, Ron Savage  wrote:

> Hi David
>
> On 28/09/16 21:43, David Cantrell wrote:
>
>> On Wed, Sep 28, 2016 at 03:10:58AM +0200, Eirik Berg Hanssen wrote:
>>
>>   Data::Dumper and a whole slew of other modules are specified as
>>> "configure" prereqs.
>>>
>>
>> The 'configure' step is when you run Makefile.PL. And because there's no
>> META.yml, the only way to find out what the configure_requires modules
>> are is to run Makefile.PL. By the time that has put the resulting data
>> into Makefile it's too late to actually *use* that data.
>>
>> Change the CONFIGURE_REQUIRES to BUILD_REQUIRES and CPAN clients should
>> DTRT.
>>
>
> Thanx!
>
>
> --
> Ron Savage - savage.net.au
>

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-28 Thread Ron Savage 

Hi David

On 28/09/16 21:43, David Cantrell wrote:

On Wed, Sep 28, 2016 at 03:10:58AM +0200, Eirik Berg Hanssen wrote:


  Data::Dumper and a whole slew of other modules are specified as
"configure" prereqs.


The 'configure' step is when you run Makefile.PL. And because there's no
META.yml, the only way to find out what the configure_requires modules
are is to run Makefile.PL. By the time that has put the resulting data
into Makefile it's too late to actually *use* that data.

Change the CONFIGURE_REQUIRES to BUILD_REQUIRES and CPAN clients should
DTRT.


Thanx!

--
Ron Savage - savage.net.au

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-28 Thread David Cantrell 
On Wed, Sep 28, 2016 at 03:10:58AM +0200, Eirik Berg Hanssen wrote:

>   Data::Dumper and a whole slew of other modules are specified as
> "configure" prereqs.

The 'configure' step is when you run Makefile.PL. And because there's no
META.yml, the only way to find out what the configure_requires modules
are is to run Makefile.PL. By the time that has put the resulting data
into Makefile it's too late to actually *use* that data.

Change the CONFIGURE_REQUIRES to BUILD_REQUIRES and CPAN clients should
DTRT.

-- 
David Cantrell | Minister for Arbitrary Justice

"The whole aim of practical politics is to keep the populace alarmed
 (and hence clamorous to be led to safety) by menacing it with an
 endless series of hobgoblins, all of them imaginary"  -- H. L. Mencken

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-27 Thread Ron Savage 

Hi Eirik

On 28/09/16 11:10, Eirik Berg Hanssen wrote:

On Wed, Sep 28, 2016 at 2:51 AM, Ron Savage > wrote:

On 28/09/16 10:47, Karen Etheridge wrote:

There's no META.* files, which probably doesn't help... if the
smoker is
taking shortcuts and expecting to find a META.* (which it shouldn't)
without running Makefile.PL, then that would explain why the smoke
report is reporting no prereqs at all.


  Actually, it reports ExtUtils::MakeMaker (0) as a prereq.


Thanx. The Makefile generates MYMETA.(json, yaml), but not META.*.


  … and the MYMETA.json that's generated when I run it here (yay
insomnia!), specifies ExtUtils::MakeMaker (0) as the only "build" prereq.

  Data::Dumper and a whole slew of other modules are specified as
"configure" prereqs.


Indeed. Makefile (I'm on Debian) contains:

#   MakeMaker Parameters:

# ABSTRACT => q[Release 3 of Marpa]
# AUTHOR => [q[Jeffrey Kegler]]
# BUILD_REQUIRES => {  }
# CONFIGURE_REQUIRES => { CPAN::Meta::Converter=>q[2.120921], 
Carp=>q[1.11], Config::AutoConf=>q[0.22], Cwd=>q[3.2501], 
Data::Dumper=>q[2.125], DynaLoader=>q[1.08], English=>q[1.04], 
Exporter=>q[5.62], ExtUtils::CBuilder=>q[0.27], 
ExtUtils::MakeMaker=>q[6.48], ExtUtils::Manifest=>q[1.51_01], 
ExtUtils::Mkbootstrap=>q[6.42], Fatal=>q[1.05], File::Copy=>q[2.11], 
File::Spec=>q[3.2501], IPC::Cmd=>q[0.40_1], List::Util=>q[1.21], 
Scalar::Util=>q[1.21], Test::More=>q[0.94], Time::Piece=>q[1.12], 
XSLoader=>q[0.08] }




  Might it be that the smoker is for some or other reason (overwrite
instead of merge?) seeing only the "build" prereqs?

  … though, shouldn't (most of?) those prereqs be "runtime" prereqs?


Yep.

Sounds like a fault with the highly-customized Makefile.PL to me.

Thanx!

--
Ron Savage - savage.net.au

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-27 Thread Eirik Berg Hanssen 
On Wed, Sep 28, 2016 at 2:51 AM, Ron Savage  wrote:

> On 28/09/16 10:47, Karen Etheridge wrote:
>
>> There's no META.* files, which probably doesn't help... if the smoker is
>> taking shortcuts and expecting to find a META.* (which it shouldn't)
>> without running Makefile.PL, then that would explain why the smoke
>> report is reporting no prereqs at all.
>>
>
  Actually, it reports ExtUtils::MakeMaker (0) as a prereq.


> Thanx. The Makefile generates MYMETA.(json, yaml), but not META.*.


  … and the MYMETA.json that's generated when I run it here (yay
insomnia!), specifies ExtUtils::MakeMaker (0) as the only "build" prereq.

  Data::Dumper and a whole slew of other modules are specified as
"configure" prereqs.

  Might it be that the smoker is for some or other reason (overwrite
instead of merge?) seeing only the "build" prereqs?

  … though, shouldn't (most of?) those prereqs be "runtime" prereqs?


Eirik

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-27 Thread Ron Savage 

Hi Karen

On 28/09/16 10:57, Karen Etheridge wrote:

META.json and META.yml are supposed to be included in the uploaded
tarball. They would be produced via 'perl Makefile.PL && make && make
test && make manifest && make dist'.


Then Jeffrey must not be using that incantation. I'll let him know 
pronto. $many x $thanx.



On Tue, Sep 27, 2016 at 5:51 PM, Ron Savage > wrote:

Hi Karen

On 28/09/16 10:47, Karen Etheridge wrote:

There's no META.* files, which probably doesn't help... if the
smoker is
taking shortcuts and expecting to find a META.* (which it shouldn't)
without running Makefile.PL, then that would explain why the smoke
report is reporting no prereqs at all.


Thanx. The Makefile generates MYMETA.(json, yaml), but not META.*.

Also, I'm on the mailing list, so one reply is OK!

On Tue, Sep 27, 2016 at 5:29 PM, Ron Savage 
>> wrote:

Hi

Data::Dumper V 2.125 is requested in the Makefile.PL.

Marpa::R3 is getting this error:



http://www.cpantesters.org/cpan/report/e20e-818f-11e6-9919-d235d7926715




>

Any ideas why V 2.125 is not being installed?

Is it because Data::Dumper is in core?

--
Ron Savage - savage.net.au 




--
Ron Savage - savage.net.au 




--
Ron Savage - savage.net.au

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-27 Thread Karen Etheridge 
META.json and META.yml are supposed to be included in the uploaded tarball.
They would be produced via 'perl Makefile.PL && make && make test && make
manifest && make dist'.

On Tue, Sep 27, 2016 at 5:51 PM, Ron Savage  wrote:

> Hi Karen
>
> On 28/09/16 10:47, Karen Etheridge wrote:
>
>> There's no META.* files, which probably doesn't help... if the smoker is
>> taking shortcuts and expecting to find a META.* (which it shouldn't)
>> without running Makefile.PL, then that would explain why the smoke
>> report is reporting no prereqs at all.
>>
>
> Thanx. The Makefile generates MYMETA.(json, yaml), but not META.*.
>
> Also, I'm on the mailing list, so one reply is OK!
>
> On Tue, Sep 27, 2016 at 5:29 PM, Ron Savage > > wrote:
>>
>> Hi
>>
>> Data::Dumper V 2.125 is requested in the Makefile.PL.
>>
>> Marpa::R3 is getting this error:
>>
>> http://www.cpantesters.org/cpan/report/e20e-818f-11e6-
>> 9919-d235d7926715
>> > 9919-d235d7926715>
>>
>> Any ideas why V 2.125 is not being installed?
>>
>> Is it because Data::Dumper is in core?
>>
>> --
>> Ron Savage - savage.net.au 
>>
>>
>>
> --
> Ron Savage - savage.net.au
>

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-27 Thread Ron Savage 

Hi Karen

On 28/09/16 10:47, Karen Etheridge wrote:

There's no META.* files, which probably doesn't help... if the smoker is
taking shortcuts and expecting to find a META.* (which it shouldn't)
without running Makefile.PL, then that would explain why the smoke
report is reporting no prereqs at all.


Thanx. The Makefile generates MYMETA.(json, yaml), but not META.*.

Also, I'm on the mailing list, so one reply is OK!


On Tue, Sep 27, 2016 at 5:29 PM, Ron Savage > wrote:

Hi

Data::Dumper V 2.125 is requested in the Makefile.PL.

Marpa::R3 is getting this error:

http://www.cpantesters.org/cpan/report/e20e-818f-11e6-9919-d235d7926715



Any ideas why V 2.125 is not being installed?

Is it because Data::Dumper is in core?

--
Ron Savage - savage.net.au 




--
Ron Savage - savage.net.au

Re: Data::Dumper issue: V 2.124 'v' 2.125

2016-09-27 Thread Karen Etheridge 
There's no META.* files, which probably doesn't help... if the smoker is
taking shortcuts and expecting to find a META.* (which it shouldn't)
without running Makefile.PL, then that would explain why the smoke report
is reporting no prereqs at all.

On Tue, Sep 27, 2016 at 5:29 PM, Ron Savage  wrote:

> Hi
>
> Data::Dumper V 2.125 is requested in the Makefile.PL.
>
> Marpa::R3 is getting this error:
>
> http://www.cpantesters.org/cpan/report/e20e-818f-11e6-
> 9919-d235d7926715
>
> Any ideas why V 2.125 is not being installed?
>
> Is it because Data::Dumper is in core?
>
> --
> Ron Savage - savage.net.au
>

Data::Dumper issue: V 2.124 'v' 2.125

2016-09-27 Thread Ron Savage 

Hi

Data::Dumper V 2.125 is requested in the Makefile.PL.

Marpa::R3 is getting this error:

http://www.cpantesters.org/cpan/report/e20e-818f-11e6-9919-d235d7926715

Any ideas why V 2.125 is not being installed?

Is it because Data::Dumper is in core?

--
Ron Savage - savage.net.au