On Mon Oct 02 08:19:33 2017, NHORNE wrote:
Show quoted text> On Mon Oct 02 07:15:47 2017, REHSACK wrote:
> > User error.
> >
> > Please use one of:
> >
> > $ perl Makefile.PL -pm
> > $ env PERL_MM_OPT=PUREPERL_ONLY=1 perl Makefile.PL
>
> Making the documentation less obscure would have helped avoid this.
Please blame the toolchain people regarding that. I'm following a 4 year old consensus of the toolchain people:
https://github.com/Perl-Toolchain-Gang/toolchain-site/blob/master/lancaster-consensus.md
And last but not least: List::MoreUtils-0.425 is release on 6th Sep 2017 - your issue is from 29th Sep 2017. Why didn't you prove at the very first whether an upgraded version of the module already solves your problem?
Show quoted text> >
> > And do not write the Makefile 3 times and expect that the options
> > stack.
>
> Nobody expects that. You understand that I was putting in all the
> methods that I tried so that you had information, right?
That's not true.
http://bfy.tw/EFEv will prove you're wrong.
In case you wonder how to get the search - please carefully review your submitted output of Makefile.PL:
Show quoted text> $ perl Makefile.PL -pm
> -pm is depreciated, please use PUREPERL_ONLY=1 where applicable. at Makefile.PL line 19.
> Generating a Unix-style Makefile
> Writing Makefile for List::MoreUtils
> Writing MYMETA.yml and MYMETA.json
Show quoted text> $ perl Makefile.PL PUREPERL_ONLY=1
> 'PUREPERL_ONLY' is not a known MakeMaker parameter name.
> Generating a Unix-style Makefile
> Writing Makefile for List::MoreUtils
> Writing MYMETA.yml and MYMETA.json
Both ones would have worked fine - even if the 2nd isn't supported and the first is depreciated and discouraged. You didn't even try. Three times!
Don't blame or flame me about that!
Best regards,
Jens