做 perlbrew 以來,一直覺得必須要提供夠充分的文件來給眾多指令提供說明。於是一開始就有做 `perlbrew help <CMD>` 這種方便讓人查 CMD 用法的 `help` 指令...
但都這麼多年了,今天我才發現 `help` 本身沒有文件。也就是 `perlbrew help help` 只會印出「找不到文件」。
這真是太糟糕了啊!
( 有人要送 PR 來嗎 ? => https://github.com/gugod/App-perlbrew/ )
@mjgardner @randomgeek @leonerd This is probably a very stupid question, but is #asdf like #perlbrew for multiple different languages ?
@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
@mjgardner @leonerd @pjakobs I just use #perlbrew for this, though the shebang gets in the way
@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