#plenv — Public Fediverse posts

@ChristosArgyrop @leonerd @pjakobs #!/usr/bin/env perl

is the typical way to call whatever #perl happens to be first in your environment's path

The nice thing about #asdf is it reads a `.tool-versions` file in a given project's directory and will use the specified perl, ruby, node, whatever version via its shim scripts: https://asdf-vm.com/guide/getting-started.html#_6-set-a-version

I used to use #plenv, which is like #perlbrew plus asdf but for Perl only: https://github.com/tokuhirom/plenv

@funkatron
@Perl Someday I should write up how I manage #Perl projects with #asdf and #direnv. Everyone talks about #perlbrew and sometimes #plenv, but it’s nice to have a single way to manage local project environments for any #programming language, especially when the project has a stack of languages and runtimes that you want to specify in one place.

@lolzac @ramsey @dmnelson @scriptingosx Oddly, #Apple has not been terrible in keeping #perl somewhat recent on #macOS: #Ventura ships with v5.30.3 from 2020.

But most advise not messing with an OS or distro’s system runtimes, especially if you want to install or upgrade libraries and modules from #CPAN etc.

The two main Perl solutions are #perlbrew: http://perlbrew.pl

And #plenv (used to be my fave): https://github.com/tokuhirom/plenv

@rrwo @profoundlynerdy @leonerd I’ve never heard of any *other* language ecosystem supporting multiple package branches at scale. Doesn't mean it can't or shouldn't be done, though, for the reasons you mention.

Now that we have quite a number of years’ experience with #perlbrew, #plenv, and #Docker #containers under our belt, adapting the #Perl toolchain and #CPAN to support multiple release branches sounds like an interesting project.