Skip Menu |

This queue is for tickets about the Sys-Info CPAN distribution.

Report information
The Basics
Id: 120898
Status: resolved
Priority: 0/
Queue: Sys-Info

People
Owner: Nobody in particular
Requestors: jkeenan [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.78
Fixed in: 0.7811



Subject: Sys-Info: Configuration fails on perl 5 blead: no dot in default @INC
In Perl 5.26.0, '.' will no longer be found by default in @INC. One consequence of this is that in statements such as: do $file; will fail if $file is simply 'some_file'. It will have to be './some_file'. Attached is a patch that will enable Makefile.PL to complete successfully. Please evaluate and, if it is acceptable, generate a new CPAN release. Thank you very much. Jim Keenan
Subject: Sys-Info.20170402.diff
--- builder/Build/Spec.pm.orig 2017-04-02 21:06:57.323956342 -0400 +++ builder/Build/Spec.pm 2017-04-02 21:08:10.471136769 -0400 @@ -17,7 +17,7 @@ } sub spec { - my $file = 'SPEC'; + my $file = './SPEC'; my $spec = do $file; my %rv =
Can someone please explain how that Makefile.PL or builder/ gets into this dist? It is not part of the git repo but probably auto-generated. But I don't know how. I only see a SPEC file in git, not sure to which of the installers this belongs, I seem to have lost track what's happening in CPAN. :-) Probably simply re-uploading new releases wiht new builder version would solve that problem. Same for all other Sys::Info modules. Steffen On Sun Apr 02 21:14:25 2017, JKEENAN wrote: Show quoted text
> In Perl 5.26.0, '.' will no longer be found by default in @INC. One > consequence of this is that in statements such as: > > do $file; > > will fail if $file is simply 'some_file'. It will have to be > './some_file'. > > Attached is a patch that will enable Makefile.PL to complete > successfully. Please evaluate and, if it is acceptable, generate a > new CPAN release. > > Thank you very much. > Jim Keenan
-- Steffen Schwigon <ss5@renormalist.net> Dresden Perl Mongers <http://dresden-pm.org/>
This is now fixed.