|There's more than one way to do things|
Hello, thank you for the help and advice, I'm a bit lost and I think I need a bit more help :-( sorry. Let me start over... here's my scenario:
The only requirement is that an install site has Perl installed and nothing else from CPAN. A site will download the software app distro into a directory $APP_HOME
The software distro comes with all non-CORE and non-XS CPAN dependencies in $APP_HOME/extlib/lib/perl5 (which I installed via cpanm -L extlib <module>) and it's own module library in $APP_HOME/lib
Programs in the software distro, lets say in $APP_HOME/scripts will need to use extlib and lib I imagine they would have this in at the top:
I would like everything to be self-contained within the app distro, therefore no meddling with the install user's .bashrc or anything like that because of multiple reasons, one being that the install user might not be the user actually running software.
local::lib is not in Perl CORE and I could have it already in extlib/lib/perl5 but then you have this chicken-egg problem. Or is local::lib not really what I want? I am not interested in the local::lib functionality to allow a user to have their own CPAN modules installed in their $HOME directory, I am interested in providing a software application distro with non-CORE dependencies already included and a way for the distro's programs to use these included library paths all in a self-contained manner. What is the recommended and standard way to do this in Perl?
In reply to Re^5: Best strategy to facilitate dependency installation for a Perl-based software distribution