OK - perhaps an explanation of the bigger picture:
At work, we have Big Iron, and run multiple services from one platform.
We also install a relatively recent Perl to replace the old one that comes with the OS.
This means that multiple services, developed by multiple developers, can be using the same core Perl installation.
This is A Good Thing[tm] as it means only one perl suite needs to be maintained
This is A Bad Thing[tm] as it means that indiscriminately adding new (or updating!) packages can have consequences for other developers and other services
It means that the additional packages I want for my service(s), I need to install (and maintain) locally..... things like Mod-Perl, like Catalyst & Moose, like adding & removing various packages until I find the right one for handling .zip files...
.... but it also means I can install these packages when I want, and not rely on another team to add it to their list of jobs.
... this doesn't answer the other interesting question - why is there a proliferation of directories, and what is it that means one goes in one place and another goes somewhere else?
I install my home-grown packages under /h/o/m/e/perl5/lib/perl/site-perl as they are local to my site.... and not part of CPAN.
In reply to Re^4: Why does PERL5LIB need to be so verbose? ( shebang )
by kiz
in thread Why does PERL5LIB need to be so verbose?
by kiz
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |