E
ethandbrown
Hi Group--
I'm having trouble deploying some code on my webhost's server because
of module incompatibilities. I'm able to install the latest CPAN
modules in my own account space, but I'm running into compatibility
issues because the default modules installed in the system directories
can be out of date with respect to the newer modules I'm installing.
I'd like to cleanly install the most current set of modules in my own
account space, but I'm not sure how to tell the CPAN module to consider
only my module path during its builds so that the newest dependent
modules are also installed (and the system modules are ignored). In my
own programs I can just set:
@INC = ("/home/myaccount/myperllibs/lib");
but I'm unclear as to how to do this while running "perl -MCPAN -e
shell"
I've reviewed the CPAN docs and saw "How to install modules in your own
space", but they don't make mention of specifying a custom "@INC" while
doing it (or I just missed it).
Help is appreciated. Thanks,
--Ethan
I'm having trouble deploying some code on my webhost's server because
of module incompatibilities. I'm able to install the latest CPAN
modules in my own account space, but I'm running into compatibility
issues because the default modules installed in the system directories
can be out of date with respect to the newer modules I'm installing.
I'd like to cleanly install the most current set of modules in my own
account space, but I'm not sure how to tell the CPAN module to consider
only my module path during its builds so that the newest dependent
modules are also installed (and the system modules are ignored). In my
own programs I can just set:
@INC = ("/home/myaccount/myperllibs/lib");
but I'm unclear as to how to do this while running "perl -MCPAN -e
shell"
I've reviewed the CPAN docs and saw "How to install modules in your own
space", but they don't make mention of specifying a custom "@INC" while
doing it (or I just missed it).
Help is appreciated. Thanks,
--Ethan