4 ms·
Here's a n00b but honest question: what is the current "best practice" method of managing Perl versions on macOS? Does Perl have anything comparable to pyenv or
by wyclif 7y ago
Here's a n00b but honest question: what is the current "best practice" method of managing Perl versions on macOS? Does Perl have anything comparable to pyenv or rbenv, or do people generally use perlbrew?
- freyfogle 7y agoperlbrew works great for me, never had a reason to seek a different solution
- xeeeeeeeeeeenu 7y agoThere are at least two solutions, perlbrew[1] and plenv[2]. Personally, I prefer perlbrew. [1] - https://perlbrew.pl https://perlbrew.pl [2] - https://github.com/tokuhirom/plenv https://github.com/tokuhirom/plenv
- petre 7y agoWe use plenv after trying perlbrew. It's shell based, doesn't require perl. The Perl-Build plugin does, however. It has straightforward documentation and creates shims instead of relying on aliases.
- FRidh 7y agoNixpkgs supports multiple versions of Perl and allows you to use them side-by-side.
- senorsmile 7y agoI always use plenv for this. Not specifically related to your question, but carton is also a must: https://metacpan.org/pod/Carton https://metacpan.org/pod/Carton
- wyclif 7y agoYeah, after installing it earlier today and using it for the first time plenv makes sense to me because I'm also using shims over in pyenv- and rbenv-land, so I set it up like this: $ echo 'eval "$(plenv init - zsh)"' >> ~/.zshrc There's a consistency to them all doing essentially the same thing on my rig (i.e. instead of exporting shell functions to switch PATH).