-
Notifications
You must be signed in to change notification settings - Fork 216
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perlbrew should manage PERL5LIB/PERL_MM_OPT/PERL_MB_OPT #513
Comments
You should be using 'perlbrew lib' to have per-perlbrew local::libs. Stacking local::lib outside perlbrew doesn't make any sense since local::lib is per perl. Please use the already written perlbrew local::lib support. |
It seems should be first thing to remove Sad that it was not mentioned in the DOC. |
I also second what @shadowcat-mst says: "local::lib is per perl". What we could do here is maybe just detecting the this 3-var settings of local::lib and produce some warn in bashrc (bootstrap time). |
On Mon, Jun 06, 2016 at 02:58:02PM -0700, Kang-min Liu wrote:
Detecting PERL_LOCAL_LIB_ROOT seems like maybe it would work? Though I do wonder if e.g. PERL5LIB is likely to be a footgun even sans a full Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue http://shadowcat.co.uk/blog/matt-s-trout/ http://twitter.com/shadowcat_mst/ Email me now on mst (at) shadowcat.co.uk and let's chat about how our CPAN |
Before perlbrew I use this variables to install perl and perl libs into $HOME.
I do next in `~/.bashrc
So when I install module I install it into my
$HOME
and do not interfere with system perl.But now I need to install
perl-5.12
and I useperlbrew
This variables cause some problems and perl segfaults because of mix of my local modules and perlbrew's. Also I note that under perlbrew modules are installed into my local dir, not perlbrew's one. And this break my local perl.
Here I switch to use perl-5.12.5 and install module:
It seems perlbrew should check
PERL5LIB/PERL_MM_OPT/PERL_MB_OPT
and alter them to make things work correct.Seems related: #414 #325 #387 #479 #211
The text was updated successfully, but these errors were encountered: