Re^5: Clean smoke-test install for Inline based modules using Inline::MakeMaker

Hammered? Its much ado about nothing

Yeah, I feel much the same way - but I have some respect for the wishes of those who expect their modules to build straight out of the box in the cpan shell, no failures and no NA/UNKNOWN.

The problem with your BEGIN{} block is that it doesn't tell the cpan shell to fetch and install the package that contains Inline::MakeMaker. If it was *my* module, that wouldn't bother me in the slightest, but many people expect better.

The second attempt looks promising - it might even provide the desired behaviour. (Does it ? The thing is that, when it comes to finally build the module, it's Inline::MakeMaker, not ExtUtils::MakeMaker, that needs to be loaded by the Makefile.PL.)
There's actually no need to specify Inline::MakeMaker in PREREQ_PM, as installing Inline::CPP will install Inline::MakeMaker.
I think that might actually work !!

But its a whole bunch of effort to avoid ... switching to Module::Install

And well worth the effort, imo. (But, again, this is not necessarily a view shared by the perl community at large.)

Cheers,
Rob

Comment on Re^5: Clean smoke-test install for Inline based modules using Inline::MakeMaker

Replies are listed 'Best First'.
Re^6: Clean smoke-test install for Inline based modules using Inline::MakeMaker by Anonymous Monk on Dec 15, 2011 at 11:08 UTC
The second attempt looks promising - it might even provide the desired behaviour. (Does it ? ... AFAIK it should, I'm 90% that it will, but if it doesn't, this ought to fix it (should force make to rerun Makefile.PL with Inline::MakeMaker ) `END { if( not exist $INC{'Inline/MakeMaker.pm'} ){ $atime = $mtime = time + 10 ; utime $atime, $mtime, 'Makefile.PL'; } }` [download]	[reply] [d/l]