I have run into the exact same problem on the script server I set up for my alliance on Lacuna Expanse.
I've found that editing the metadata files for the perlbrew installation in the new user's home directory (and the new user's .bashrc/.bash_profile) is the way to correct the path problem. It really was quite simple, even though it wasn't automated.
For an automated solution, a quick search/replace script could be created to do the path corrections for you in the appropriate files.
One final point of advice: Look in the ~/.cpanm / ~/.perlbrew/ directories for any conf files that need updating as well. As the new user, run the cpanm command on a simple module to make sure you got it right.
Good luck!
In reply to Re: How to provide an isolated Perl environment for newly added users?
by Tommy
in thread How to provide an isolated Perl environment for newly added users?
by walkingthecow
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |