activating lib root writes full PATH etc into init file

[haarg]

If a lib directory is activated, the PATH and other environment variables are written into the .perlbrew/init file. When starting a new shell, these then overwrite any set prior in the shell's rc file.

[gugod]

@Haar, Sorry I don't understand the point you're making here. Can you maybe provide me some steps that demonstrate the issue ?

[Haar]

Typo there, wrong person :).

[haarg]

If you install and switch to a normal perl version, the init file, which is sourced by the bashrc file, looks like this:
export PERLBREW_MANPATH="/Users/gknop/perl5/perlbrew/perls/perl-5.16.0/man"
export PERLBREW_PERL="perl-5.16.0"
export PERLBREW_VERSION="0.44"
export PERLBREW_PATH="/Users/gknop/perl5/perlbrew/bin:/Users/gknop/perl5/perlbrew/perls/perl-5.16.0/bin"
export PERLBREW_ROOT="/Users/gknop/perl5/perlbrew"

If you activate a local::lib path, as created with the perlbrew lib command, it looks like this:
export PERLBREW_PERL="perl-5.16.0"
export PERLBREW_VERSION="0.44"
export PERL_MB_OPT="--install_base /Users/gknop/.perlbrew/libs/perl-5.16.0@base"
export PERL_LOCAL_LIB_ROOT="/Users/gknop/.perlbrew/libs/perl-5.16.0@base"
export PERL_MM_OPT="INSTALL_BASE=/Users/gknop/.perlbrew/libs/perl-5.16.0@base"
export PERL5LIB="/Users/gknop/.perlbrew/libs/perl-5.16.0@base/lib/perl5/darwin-thread-multi-2level:/Users/gknop/.perlbrew/libs/perl-5.16.0@base/lib/perl5:/Users/gknop/.local-lib/lib/perl5/darwin-thread-multi-2level:/Users/gknop/.local-lib/lib/perl5"
export PATH="/Users/gknop/perl5/perlbrew/bin:/Users/gknop/perl5/perlbrew/perls/perl-5.16.0/bin:/Users/gknop/bin:/Users/gknop/Library/Python/2.7/bin:/Users/gknop/.gem/ruby/1.8/bin:/usr/local/mysql/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin"
export PERLBREW_MANPATH="/Users/gknop/.perlbrew/libs/perl-5.16.0@base/man:/Users/gknop/perl5/perlbrew/perls/perl-5.16.0/man"
export PERLBREW_LIB="base"
export PERLBREW_PATH="/Users/gknop/.perlbrew/libs/perl-5.16.0@base/bin:/Users/gknop/perl5/perlbrew/bin:/Users/gknop/perl5/perlbrew/perls/perl-5.16.0/bin"
export PERLBREW_ROOT="/Users/gknop/perl5/perlbrew"

This file is sourced during the bashrc file, which means any changes prior to sourcing it are wiped out.

[gugod]

On 2012/7/13, at 下午4:07, Graham Knop wrote:

If you activate a local::lib path, as created with the perlbrew lib command, it looks like this:
export PERLBREW_PERL="perl-5.16.0"
export PERLBREW_VERSION="0.44"
export PERL_MB_OPT="--install_base /Users/gknop/.perlbrew/libs/perl-5.16.0@base"
export PERL_LOCAL_LIB_ROOT="/Users/gknop/.perlbrew/libs/perl-5.16.0@base"
export PERL_MM_OPT="INSTALL_BASE=/Users/gknop/.perlbrew/libs/perl-5.16.0@base"
export PERL5LIB="/Users/gknop/.perlbrew/libs/perl-5.16.0@base/lib/perl5/darwin-thread-multi-2level:/Users/gknop/.perlbrew/libs/perl-5.16.0@base/lib/perl5:/Users/gknop/.local-lib/lib/perl5/darwin-thread-multi-2level:/Users/gknop/.local-lib/lib/perl5"
export PATH="/Users/gknop/perl5/perlbrew/bin:/Users/gknop/perl5/perlbrew/perls/perl-5.16.0/bin:/Users/gknop/bin:/Users/gknop/Library/Python/2.7/bin:/Users/gknop/.gem/ruby/1.8/bin:/usr/local/mysql/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11/bin"
export PERLBREW_MANPATH="/Users/gknop/.perlbrew/libs/perl-5.16.0@base/man:/Users/gknop/perl5/perlbrew/perls/perl-5.16.0/man"
export PERLBREW_LIB="base"
export PERLBREW_PATH="/Users/gknop/.perlbrew/libs/perl-5.16.0@base/bin:/Users/gknop/perl5/perlbrew/bin:/Users/gknop/perl5/perlbrew/perls/perl-5.16.0/bin"
export PERLBREW_ROOT="/Users/gknop/perl5/perlbrew"

This file is sourced during the bashrc file, which means any changes prior to sourcing it are wiped out.

True. But that's the coded and intended behavior. What trouble or issue are you exactly dealing with ?

Cheers,
Kang-min Liu

[haarg]

It's a problem because it is overwriting the PATH instead of adding to it.

If your bashrc makes any changes to PATH before sourcing the perlbrew rc file, they are overwritten. Additions to PATH after sourcing the rc file get written to the init file, so the next time they are added they add duplicate entries.

The direct case I ran into was a bug in my bashrc file, and after fixing it I couldn't get the fix to apply until after I tracked it down to perlbrew overwriting my changes.

[gugod]

@haarg,

Ah, right. I see the problem now. It looks like PATH, PERL5LIB, and PERL_* should all be removed from there.

[rjbs]

I just hit this bug. I updated my $PATH in .zshrc and it kept getting re-ordered the old way. I was so confused until I started tracing everything. I am excited to see that it's already been identified as a problem!

[haarg]

It looks to me like this has been fixed.

[gugod]

@haarg Thanks for the write up. Closing this issue.