plenv VS App-perlbrew

So here it is, a PR with a new implementation of Perlbrew support to the latest version of Liquidprompt and as a bonus, I also added support for plenv and alternative to Perlbrew for handling your Perl installations.

If you don’t care that the version isn’t exactly the same 100% of the time, you can use do sh perlbrew clone-modules (that’s plenv migrate-modules for plenv users). If you want real dependency pinning per project you’re better off using something like Carmel on top of perlbrew or plenv so you can specify what versions of each module you want in your cpanfile, run carmel install whenever you switch to another perl version, and then it should just be a matter of letting Carmel find/load the right versions of each module for you with carmel exec …

Since perlbrew has wholly met my needs, I have not spent much time with plenv. This is not a critique, just my point of view. One warning contained in the plenv read me is:

Nice article. You mention preferring plenv but you only give it passing mention. It would be nice if the article also explained the installation process for that.

Virtual envs are not as much vital in Perl, but there is plenv or perlbrew

Perl perlbrew and plenv is same as Python pyenv.

(Advanced users may want to investigate using perlbrew, plenv, or berrybrew for managing multiple versions of Perl and installing more recent versions than are included on your system.)

Perlbrew on github

Note that this Oracle Linux VM comes with Perl 5.26, if you want a more recent version, you could use use Perlbrew.

Install your own Perl with perlbrew, instead of using the system Perl. Then every needed dependency is installed in an isolated Perl with cpanm.

The final and most exciting way to call --init is with a Perl version number. When called with a version number, Plx will look for a Perl of the given version first in your PATH and otherwise via Perlbrew.

perlbrew is a command line tool to intall Perl on user directries. You can install any version of Perl on your user directries and use it.

Can't perlbrew be an option? AFAIK, it installs the Perl of your choice "next to" the Perl that comes with the OS, so both will continue to work.