Re^5: Requring minimum perl version in a cpanfile ( use lib '.'; )

Replies are listed 'Best First'.
Re^6: Requring minimum perl version in a cpanfile ( use lib '.'; ) by Corion (Patriarch) on Jan 20, 2017 at 08:01 UTC
I interpret this discussion towards the idea of not supporting `.` in `@INC` in the future for somewhat plausible security reasons. Note that this would not prevent manually adding dot to `@INC`. Update: Also see this bug ticket, which I think was the original report.	[reply] [d/l] [select]
Re^7: Requring minimum perl version in a cpanfile ( use lib '.'; ) by Anonymous Monk on Jan 20, 2017 at 08:22 UTC
Heheh, ok this But I have another proposal. Instead of modifying CPAN clients, builders and App::Prove to inject '.' into @INC, what about instead injecting in @INC the *absolute path of the root of the distribution* being configured/built/tested/installed? I think that this would considerably reduce the number of side effects and it would help to really isolate runtime code that relies on '.' being in @INC (assuming that code is covered by a testsuite).	[reply]
Re^8: Requring minimum perl version in a cpanfile ( use lib '.'; ) by Corion (Patriarch) on Jan 20, 2017 at 08:33 UTC
Yes, if they do that, I think that should solve all these problems, and it's certainly better than adding the current directory as "`.`". In any case, I think it helps to be aware of the potential issue when using `inc/`-style module distribution/installation kits, especially when they won't get automatically updated ;)	[reply] [d/l] [select]
Re^8: Requring minimum perl version in a cpanfile ( use lib '.'; ) by Anonymous Monk on Jan 20, 2017 at 23:15 UTC
Well that was quick http://search.cpan.org/~shay/perl-5.24.1/pod/perldelta.pod#Core_modules_and_tools_no_longer_search_%22.%22_for_optional_modules	[reply]