develooper Front page | perl.perl5.porters | Postings from December 2016

Re: Should we bring in Module::Runtime into core?

Thread Previous
James E Keenan
December 5, 2016 01:02
Re: Should we bring in Module::Runtime into core?
Message ID:
On 12/04/2016 07:55 PM, Craig A. Berry wrote:
> On Sun, Dec 4, 2016 at 4:44 PM, James E Keenan <> wrote:
>> 1. I notice that on CPAN Module::Runtime is fundamentally built from
>> Module::Build.  Its Makefile.PL is "auto-generated by Module::Build::Compat
>> version 0.4204."  But we no longer carry Module::Build in core.  That means
>> we would need a "pure" Makefile.PL, i.e., one generated by
>> ExtUtils::MakeMaker -- correct?
> It's exactly *one* .pm file of a couple dozen lines of code plus
> comments plus tests and metadata.  Worst case is copy that one file to
> lib/ and find somewhere to put the tests.  But most likely the
> "just_pm_to_blib" feature of would be completely adequate
> and it could remain upstream CPAN and live under it's own cpan/
> directory in the core distribution.
> In other words, it's CPAN build dependencies are a red herring and I
> believe discussion here should focus what it's for and what problem
> having it in core would solve.

I wasn't trying to create a red herring for the purpose of preventing 
this from coming into core.  I was just raising a technical question as 
to how it would come into core.  From what I've seen so far, I think 
this would look nice in core.

I assume it's got something to do with
> being able to banish the current working directory from @INC, but
> that's a bit of a WAG.

Thread Previous Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About