Welcome to the Monastery | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I don't think you need all the system perl paths in PERL5LIB. The command perl -V will list out everything that is in @INC including all the paths that were set at perl's build time (in config.pm). Of course, you might be trying to have more than one perl on your host, and trying to share some of the library directories. I would seriously advise against that, as there could be all sorts of unforseen side effects when you come to automatically install some modules to one of the perls, see A problem with two perls on a Debian system for when I came unstuck with this. My suggestion is to keep just the user install directories, e.g. /home/gabor/perl5lib in PERL5LIB. I've had no problems with this approach. I am in a work situation where I am installing modules to a place that doesn't require root. It's actually a Clearcase vob, but that's another story. -- In reply to Re: Installing modules locally
by rinceWind
|
|