OpenSpace has asked for the wisdom of the Perl Monks concerning the following question:
Hi,
I am trying to set up Moose and to this end used perlbrew to install perl-5.20.3 to a users directory /home/grunt103 and then used perlbrews cpanm to install Moose and all it's dependencies. When the install started I was told "Can't write to /usr/local/share/perl5 and /usr/local/bin: Installing modules to /home/grunt103/perl5". The last on screen message was "Succesfully installed Moose-2.1804"
But when I run the script I get the message "Can't locate Moose.pm in @INC" even though it shows the /home/grunt103/perl5 path in @INC
If I add /home/grunt103/.cpanm/work/1466508369.14292/Moose-2.1804/lib/ to the 'use lib' path then I no longer get the "Can't locate Moose.pm" but get a variety of messages about not locating the dependencies. When I search to see where .pm modules are installed below the /home/grunt103 directory I find I have more than 400 different unique paths to the modules!
How can I rationalise this into a practical form? Or do I need a code solution to create a single access point?
Thanks for your help
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: @INC not providing path to modules
by hippo (Archbishop) on Jun 22, 2016 at 14:59 UTC | |
|
Re: @INC not providing path to modules
by perlfan (Parson) on Jun 22, 2016 at 20:05 UTC | |
by Anonymous Monk on Jun 23, 2016 at 11:23 UTC | |
by Corion (Patriarch) on Jun 23, 2016 at 11:25 UTC | |
by Anonymous Monk on Jun 23, 2016 at 11:34 UTC | |
|
Re: @INC not providing path to modules
by OpenSpace (Novice) on Jun 22, 2016 at 15:13 UTC | |
by OpenSpace (Novice) on Jun 28, 2016 at 15:00 UTC |