Kang-min Liu

@KES777 I noticed the same error when installing perl-5.8.8 on debian 8. Perhaps it also happens on recent perl versions. But basically this means we need to add something to...

The way perlbrew discover perl installation is simply by scanning the path`~/perl5/perlbrew/perls`, or `$ENV{PERLBREW_ROOT}/perls` if `$ENV{PERLBREW_ROOT}` is defined. The `perlbrew install` command does munge the default `prefix` value for Configure...

Hi @a-velt It appears to me that your "current perl" is somehow detected to be `/usr/bin/perl`, which leads to this output. This is crucial since the `list-module` command is just...

@amit4mchiba the end of that log reveals the fact that a few tests had failed, but the beginning suggest that `patchperl` itself failed to patch (probably): ``` Auto-guessed '5.14.2' patching...

This is perhaps an regression. perlbrew is supposed to detrct thar 5.37 is a dev release and do whatever adjustment for you. The symlink you've done manually (perl -> perl5.37.3)...

You are absolutely correct. entries in PERL5LIB are seperated with ":" instead of blank. cc our fish master @yanick here :)

@hoelzro: Thanks for you time to implement it. I tried it, but I decide it more works are required before it is released. It is merged as a feature branch...

perlbrew itself does not do compilation of Perl modules but only tweaks enough env variables to make `cpanm` or `cpan` install modules to the right place -- either a "site_perl"...

> * Is `perlbrew` compatible with an `env ARCHFLAGS='-arch arm64 -arch arm64e -arch x86_64' perlbrew …` approach? I haven't test it myself but I believe so. Since ARCHFLAGS is not...

Somehow this never became a problem to me... but obviously I'm blinded by my own implementation. My guess is that this is perhaps related to networking .... If the network...