> On Jan 18, 2017, at 6:49 AM, James E Keenan <jk...@verizon.net> wrote:
>
> On 01/16/2017 12:06 PM, Todd Rinaldo wrote:
>> All,
>>
>> What at this point I feel is lacking is agreement and/or discussion that the
>> above is the correct approach to solving this problem.
>>
>
> Well, since no one else has responded in this location, I will.
>
> I suppose the first step would be to open bug tickets for each of the
> distributions mentioned (github issue in the case of cpanminus). So far,
> this issue is referred to in only one ticket for CPAN.
I was asked to open a discussion rather than opening with the solution.
However, 2 months of effort has yielded almost no response. I'll be opening the
relevant tickets this weekend.
>> If you are not for this plan and/or you are a maintainer of one of the above
>> mentioned packages, your response would be appreciated. We're running out of
>> time to complete this in time for perl 5.26.
>>
>
> Have you written, or do you need to have written, any program identifying
> affected distributions on CPAN?
>
Almost all Module::Install based modules will need to be fixed for sure with a
minor change to Makefile.PL. Something along the lines of:
perl -pi -e 's/(use inc::Module::Install;)/BEGIN{push \@INC, "."}\n$1/'
Makefile.PL
Once the mentioned modules in my email are fixed, it was my hope we could
simply flip the default bit on this feature in perl and let smokers reveal the
scope of the remaining problem. I expect it to be 100-200 modules which will
need a more hand crafted fix, though it may be more like 10-20.
Todd
