in reply to Using CPAN Config.pm instead of MyConfig.pm

I'd really like to have only one configuration file so other authorized users aren't installing packages and source to the four corners of the hard drives.
In MyConfig.pm, you can define cpan_home. I am not sure if assigning something global to this key would solve your issue.

Even if everyone uses the same configuration by default, they can nevertheless call cpan -j another_config or even, horrors, install the downloaded modules manually.

Replies are listed 'Best First'.
Re^2: Using CPAN Config.pm instead of MyConfig.pm
by Only1KW (Sexton) on Jul 22, 2011 at 21:05 UTC

    I understand that other users could easily get around the default paths set in a global config file, and accept that risk. My bigger concern is users unintentionally placing modules in locations not covered by @INC rather than users that are intentionally being devious. As I said, only a few users will have the necessary permissions to install modules in a global location anyways.

[reply]

In Section Seekers of Perl Wisdom