Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

perl-5.26.0 compatibility. #11

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jkeenan
Copy link

@jkeenan jkeenan commented Apr 1, 2017

In Perl 5.26.0, '.' will no longer be found by default in @inc. This patch
adjusts Makefile.PL to accommodate that change.

For: https://rt.cpan.org/Ticket/Display.html?id=120737

In Perl 5.26.0, '.' will no longer be found by default in @inc.  This patch
adjusts Makefile.PL to accommodate that change.

For:  https://rt.cpan.org/Ticket/Display.html?id=120737
@kentfredric
Copy link

Pretty much what I'd do. 👍

And it fixes the issues I'm aware of.

@moznion
Copy link

moznion commented Jun 21, 2017

@jkeenan
IMO, it is prefer use FindBin; use lib $FindBin::Bin; rather than use lib '.';.
Because use lib '.'; handles relative path so there is a possibility to mix vulnerability. In other hand, use FindBin; use lib $FindBin::Bin; uses absolute path; so it is robust than other one.
(Though probably it is safe to use use lib '.'; on only Makefile.PL)

@kentfredric
Copy link

kentfredric commented Jun 22, 2017

using . instead of anything else is more a result of what Module::Install does inside itself. Its a horror show. Module::Install augments @INC itself in a dozen or so ways on its own ( and it tweaks %INC! Ugh! )

For anything other than Module::Install I'd not use that use lib '.' syntax.

But for Module::Install, its about as close to a right answer as you'll get.

@jjn1056
Copy link

jjn1056 commented Sep 28, 2018

This has been outstanding for a while, for a module that is pretty upstream. I emailed author at his CPAN registered Email address but not sure if @kazuho is still monitoring or even working in Perl anymore.

@jkeenan
Copy link
Author

jkeenan commented Sep 29, 2018

This has been outstanding for a while, for a module that is pretty upstream. I emailed author at his CPAN registered Email address but not sure if @kazuho is still monitoring or even working in Perl anymore.

Yes, in these situations we often have to resort to trying to find someone who knows @kazuho IRL. In the version of CPAN-river which I calculated in June for reporting to P5P, this distribution was #350.

Fortunately, neither Catalyst-Runtime nor Catalyst-Devel is a revdep :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants