Front page | perl.perl5.porters |
Postings from May 2017
On Sun, May 14, 2017 at 6:12 AM, Kent Fredric <kentfredric@gmail.com> wrote: > On 14 May 2017 at 10:33, Ãvar Arnfjörð Bjarmason <avarab@gmail.com> wrote: >> but most importantly isn't this wrong? >> + don't we have . in @INC now unless you opt-in via >> + -Ddefault_inc_excludes_dot? If not the main section above >> + needs changing. > > > -Ddefault_inc_excludes_dot is now the default, if you don't like it > the only option is to op _out_ with -Udefault_inc_excludes_dot Right, but that's the opposite of what the intro section says, it needs to be more like this: $ git diff diff --git a/pod/perldelta.pod b/pod/perldelta.pod index c8dc2b81a3..3c3b9b370b 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -64,8 +64,9 @@ prints "Hello there\n" with no leading whitespace. =head2 '.' and @INC -Perl now provides a way to build perl without C<.> in @INC by default. If you -want this feature, you can build with -Ddefault_inc_excludes_dot +For security reasons, Perl does not have C<.> in @INC by default. To +re-enable C<.> in @INC globally build perl with +C<-Udefault_inc_excludes_dot>. Because the build & test process for many Perl modules does not function well with C<.> missing from @INC, setting > The only reason there might be the perception to the contrary is due to > the side feature, PERL_USE_UNSAFE_INC, which, when set to 1, restores > '.' in @INC when perl otherwise lacks it. > > And _that_ ENV var is used in a few places in CPAN clients and TAP::Harness, > which creates confusing perceptions for maintainers, but makes things > less broken > for end users. Right, and I see that the http://www.nntp.perl.org/group/perl.perl5.porters/2017/03/msg243763.html thread pointed out on IRC has lots of proposed details about how to cover that. > > -- > Kent > > KENTNL - https://metacpan.org/author/KENTNLThread Previous | Thread Next