Welcome to the Monastery | |
PerlMonks |
installing multiple versions of same moduleby goonfest (Sexton) |
on Apr 26, 2002 at 16:30 UTC ( [id://162326]=perlquestion: print w/replies, xml ) | Need Help?? |
goonfest has asked for the wisdom of the Perl Monks concerning the following question:
Before I try it, I want to see if anyone has any insights.
I want to install version 2.0 of a perl module into a local directory. The concern is that version 1.0 of the same module already exists in the main PERL directory that I do NOT have write-access to. Of course, I could always contact the system admin to upgrade the module, but I reckon it would not be high on his priority list. In my script, I am using a standard header subroutine to pull in modules from both my local directory and the main PERL dir. I am using a "use lib" statement for each directory, thus, what will @INC contain if it sees the same module name twice? Are multiple "use lib" statments somehow prioritized, that is, will the last imported instance of a module overwrite any of those previously imported, or vice-versa? I'm sure this same issue will arise again in the future. Any other ideas(not involving the sys admin) on what I can do? Is their great risk of crashing anything? Mind you, I am doing this at work. "Be proud, be a Goon"
Back to
Seekers of Perl Wisdom
|
|