Perlbrew 0.12 cannot be used from within a bash script about app-perlbrew

[mrmuskrat]

I looked at this issue intently for a few days. The only way that I found to fix it is nothing more than a workaround; fire off perlbrew and replace the shell with exec so that the environment changes are preserved.

[gugod]

It does not seem to be possible to preserve $PATH without an exec bash after your bash script finished.

perlbrew switch should update your $HOME/.perlbrew/init file with new values. A newly invoked shell should be able to read those values again.

Basically, a source $HOME/.perlbrew/init right after your bash script finished should be sufficient. But you'll need to do it outside of your bash script.

[gugod]

@mrmuskrat, correct me if I'm understanding it wrong, are you trying to run "perlbrew use perl-5.12.2" inside your bash script ? If so, you will need to source the provided bashrc first.

If you did that and the problem remains, I suggest you to upgrade to at lease version 0.22, which, I believe, is a much robust version in terms of bash integration.

Let me know if upgrading works, or let's discuss your use case and maybe craete a Howto document for it :)

[gugod]

Just a quick not here. In the next release, to be above to perform perlbrew function in a shell script, 3 lines should be included in advance in the script:

export PERLBREW_ROOT=/opt/perlbrew
export PERLBREW_HOME=/tmp/.perlbrew
. ${PERLBREW_ROOT}/etc/bashrc

After that, perlbrew use and perlbrew switch can correctly alter $PATH in the shell script. This should also make it friendlier to be invoked from crontab.

However I still have no idea how to implement a csh counter-part. Leaving that as an exercise :)

I will write an brief article about this improvement in the next release note, therefore I am closing this issue now.