Skip Menu |

This queue is for tickets about the File-Path CPAN distribution.

Report information
The Basics
Id: 41944
Status: rejected
Priority: 0/
Queue: File-Path

People
Owner: dland [...] cpan.org
Requestors:
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 2.07
Fixed in: (no value)



Subject: cpan(1) install fails on OS X
$ cpan File::Path [...] t/taint....Can't open perl script ""-I/Users/michael/Library/Application Support/.cpan/build/File-Path-2.07-oawBVl/blib/lib"": No such file or directory I just got a MacBook. The above message failed at the command line for "cpan File::Path". After reworking my cpan(1) config in /Users/michael/Library/Aplication Support/.cpan/CPAN/MyConfig.pm to move the .cpan directory under my home directory, the install worked. As much as I despise directories with spaces, that's the OS X default. I've circumvented it, but fixing this problem will help future OS X users. In case collaboration, or common root cause analysis may point to CPAN.pm, I reported identical problem with HTML::Tree.
On Wed Dec 24 21:27:45 2008, MichaelRWolf@att.net wrote: Show quoted text
> $ cpan File::Path > [...] > t/taint....Can't open perl script ""-I/Users/michael/Library/Application > Support/.cpan/build/File-Path-2.07-oawBVl/blib/lib"": No such file or > directory > > > I just got a MacBook. The above message failed at the command line for > "cpan File::Path". After reworking my cpan(1) config in > /Users/michael/Library/Aplication Support/.cpan/CPAN/MyConfig.pm to move > the .cpan directory under my home directory, the install worked. As > much as I despise directories with spaces, that's the OS X default. > I've circumvented it, but fixing this problem will help future OS X users. > > In case collaboration, or common root cause analysis may point to > CPAN.pm, I reported identical problem with HTML::Tree.
It's number is #41944
Show quoted text
> It's number is #41944
No, *this* number is #41944. The other number is #41945.
On Wed Dec 24 21:29:39 2008, MichaelRWolf@att.net wrote: Show quoted text
> > It's number is #41944
> > No, *this* number is #41944. The other number is #41945.
Following this up after far too long... is this my or somebody else's problem? Unless I'm reading this incorrectly, I can close this ticket? Thanks, David
The target directory is protected by the operating environment. This issue is unresolvable; there is no issue installing in system perl (with privileged access), private perl distros, or perlbrew generated distros.