Branch: refs/heads/haarg/pathtools-config-before-chdir
Home: https://github.com/Perl/perl5
Commit: 85bc66764b118bcbd7510d13d13d34e426836af5
https://github.com/Perl/perl5/commit/85bc66764b118bcbd7510d13d13d34e426836af5
Author: Graham Knop <ha...@haarg.org>
Date: 2025-04-01 (Tue, 01 Apr 2025)
Changed paths:
M dist/PathTools/Cwd.pm
M dist/PathTools/lib/File/Spec.pm
M dist/PathTools/lib/File/Spec/AmigaOS.pm
M dist/PathTools/lib/File/Spec/Cygwin.pm
M dist/PathTools/lib/File/Spec/Epoc.pm
M dist/PathTools/lib/File/Spec/Functions.pm
M dist/PathTools/lib/File/Spec/Mac.pm
M dist/PathTools/lib/File/Spec/OS2.pm
M dist/PathTools/lib/File/Spec/Unix.pm
M dist/PathTools/lib/File/Spec/VMS.pm
M dist/PathTools/lib/File/Spec/Win32.pm
M dist/PathTools/t/cwd_enoent.t
Log Message:
-----------
PathTools: check Config values early before chdir
In a perl core build, the @INC paths will be relative. If you change
directories before loading all of the files needed, they won't be able
to be found. Config.pm loads some of its values at runtime, so if they
are accessed after a chdir, it may fail.
One of the PathTools tests was relying on the fact that Config_heavy.pl
would be loaded by Test::More, before it did a chdir. Newer Test::More
won't do that, so the test would fail. Accessing the required Config
values early will prevent this failure.
This same issue is unlikely to impact anything outside core, as it
requires the perl core paths in @INC to be relative paths, which is
normally not the case.
To unsubscribe from these emails, change your notification settings at
https://github.com/Perl/perl5/settings/notifications
