metacpan-web VS plenv

In January 2018, I proposed a CPAN Butterfly Plan to convert Perl functionality to Raku as closely as possible to the original API. I stated this as a goal because Perl (as a programming language) is so much more than syntax alone. Ask anyone what Perl's unique selling point is, and they will most likely tell you it is CPAN.

MetaCPAN. There are a number of project in the Perl community. This is one of the most interesting ones. source code

Perl has numerous modules for practically everything. Try a search on https://metacpan.org for anything that takes your fancy.

I can point to the module library metacpan.org that has modules to do tons of different things -- I don't know what equivalent resouorce Python has.

A good place for this issue would be https://github.com/metacpan/metacpan-web

All language package index websites are a poor imitation of metacpan.org. Without a doubt it is the single best package website I have used for finding packages, reading docs, examples, version changes, source repo. Everybody should be shamelessly copying it.

While the indicates that this is a Windows-related thing, there are a number of packages on CPAN that are in the Win32 namespace, but also work on Linux. This one, it seems does not. It seems at least one of its dependencies, the Win32-API does not work on anything else besides Windows.

A Perl distribution is an archive of files that includes a Perl module. There are no official rules on what non-module files must be included in a distribution, but they often include (among other things) test scripts, a Makefile.PL, documentation, and the license. These distributions are commonly uploaded to CPAN, which is a place for Perl programmers to upload their Perl distributions for the purpose of sharing their code.

If there are modules being used, you can read their documentation using the perldoc command or looking online at https://metacpan.org

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.)