Skip Menu |

This queue is for tickets about the Module-ScanDeps CPAN distribution.

Report information
The Basics
Id: 39642
Status: resolved
Priority: 0/
Queue: Module-ScanDeps

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

Bug Information
Severity: Unimportant
Broken in: 0.84
Fixed in: (no value)



Subject: potential issue with unexpanded directory names
scandepds.pl contains the following two lines: my $privPath = "$Config::Config{privlib}/$key"; my $archPath = "$Config::Config{archlib}/$key"; 'privlib' and 'archlib' both contain unexpanded paths (which may have a tilde in them), when I think using the expanded path would be less likely to cause a problem. There are corresponding keys for this named 'privlibexp/ and 'archlibexp'. A related discussion about the distinction: http://london.pm.org/pipermail/london.pm/Week-of-Mon-20061009/004833.html Mark
CC: par [...] perl.org
Subject: Re: [rt.cpan.org #39642] potential issue with unexpanded directory names
Date: Tue, 30 Sep 2008 09:40:51 +0200
To: bug-Module-ScanDeps [...] rt.cpan.org
From: Steffen Mueller <wyp3rlx02 [...] sneakemail.com>
Hi Mark, sorry for the delay in replying. MARKSTOS via RT wrote: Show quoted text
> Queue: Module-ScanDeps > Subject: potential issue with unexpanded directory names
[...] Show quoted text
> scandepds.pl contains the following two lines: > > my $privPath = "$Config::Config{privlib}/$key"; > my $archPath = "$Config::Config{archlib}/$key"; > > 'privlib' and 'archlib' both contain unexpanded paths (which may have a > tilde in them), when I think using the expanded path would be less > likely to cause a problem.
I'll replace the use of privlib/archlib with the corresponding expanded keys. Best regards, Steffen