David Golden wrote:
So on OSX, if your .cpan directory is under ~/Library/Application\ Support/.cpan then you should probably customize CPAN's 'build_dir' option to a path without spaces:
Which is what I did. My build/ and sources/ directory remain under ~/.cpan/; only CPAN/MyConfig.pm is in the File::HomeDir-dictated location.
[snip] History of the issue is here: http://rt.cpan.org/Public/Bug/Display.html?id=32841
I just read through that ticket. I agree with a lot of what David Wheeler said in both his OP and later posts. It's a PITA to have CPAN configuration, source, and build data in two different locations. It's also very un-Unixish to have a wordspace in a path to hold user-selected data that does not pertain to a Mac GUI application, as distinct from vendor data.
Jim Keenan
