plenv

What plenv is

plenv is a free Perl version manager for choosing which Perl a project uses. It installs Perl versions under the user’s home directory and lets users switch versions in a shell, helping align a development environment with production. A `.perl-version` file can set a project-specific version for a directory; that local selection takes precedence over the global version. Perl commands are routed through shell script wrappers called shims.

The project documents setup for Bash and Zsh, including optional shell integration and autocompletion. Users can install plenv from GitHub, an archive, or Homebrew on Mac OS X. The `perl-build` plugin provides the `plenv install` command, while `plenv-contrib` adds `use` and `lib` commands as a local::lib integration replacement. The README recommends Carton for Perl upgrades and deployments. Its `migrate-modules` command installs the newest module versions from one Perl environment into another, and those versions may differ from the original environment.

plenv supports Linux and macOS and is distributed as free software under the same terms as Perl itself. The listed dependencies are Perl 5.8.1 or later and Bash; curl is needed for `plenv install-cpanm`. plenv is incompatible with perlbrew, so existing perlbrew installations and shell initialization references must be removed before installing plenv. Bug reports can be sent through GitHub issues.

Who it suits

plenv suits Perl developers who need different Perl versions for different projects or want a development environment to match production. It is aimed at Linux and macOS users who work in Bash or Zsh and are comfortable installing a command-line tool and managing shell setup.

Limits

plenv requires Perl 5.8.1 or later and Bash; curl is required for `plenv install-cpanm`. It cannot be used alongside perlbrew, and migrated modules may have different versions in the destination environment.

Getting started

1. Visit https://github.com/tokuhirom/plenv.
2. Install plenv from GitHub, an archive, or Homebrew on Mac OS X.
3. Set up the shell using the documented Bash or Zsh instructions.
4. Optionally enable shell integration and autocompletion.
5. Use the `perl-build` plugin for the `plenv install` command, if needed.
6. Add a `.perl-version` file in a project directory to select its Perl version.

Verdict

Choose plenv if you need project-specific Perl versions on Linux or macOS and want shell-based switching. Its local version file and shims provide per-project selection, while plugins extend installation and module workflows. Look elsewhere if you need to keep using perlbrew, which is incompatible with plenv.