[ameat]

so i've been playing around with cpan, trying to install some modules (no, this isn't about DBD::*), and am getting annoyed about where the modules are installing.

i first tried setting, from within cpan, LIB=~/Library/Perl/lib and INSTALLMAN1DIR=~/Library/Perl/man/man1, etc... but when i install a module, some get placed in the directory i specified and others get buried into a directory titled "darwin-thread-multi-2level". removing the config options and installing in the default location, it again does the same thing inside /System/Library/Perl.

WHY?! i just want them to sit at the root of the specified directory. can anyone provide any reason as to why it puts the files in the darwin directory? i could manually place them where i want after the fact, but it gets kind of annoying.

thanks for your help,
amit

[Paul McCann]

The modules that end up there involve a compiled portion: that is, they're dependent on local details of your perl (how it was compiled, what sort of architecture it's running on and so forth), and that's reflected in the path you're seeing. You could, for example, have a nice unthreaded perl compiled, and its modules would sit in a directory forking off from where you're seeing the "darwin-thread-multi-2level" directory. Things are designed so that multiple installations can survive without nasty intersections causing grief.

In essence: things are behaving in a sane, sensible manner! Let CPAN install in peace!

[ameat]

thanks for the info. i figured as much. i had just never noticed the platform specific install directory since in most of the other installations that i've used, the directory name just isn't as noticeable/long.