New comment by aaFn on void-packages repository

https://github.com/void-linux/void-packages/issues/32857#issuecomment-915142915

Comment:
Correct, I also hear there are performance implications, but primarily related to threads as I get it, not to multiplicity itself (so we already have that impact in). Or let me know if I am wrong.

For now I took 2.0.34 sources from CPAN, recompiled and installed as a second perl instance in /usr/local + redirected by symlink all things like /usr/bin/perl, /usr/bin/cpan, /usr/lib/libperl.so* to my instance in /usr/local - since I cannot remove the perl xbps package because it is required by apache and other packages.

I re-compiled with no thread support at all (`-Uusethreads`), with apache in prefork mode, and with mod_perl built as dynamic module (=> using libperl.so) .. works well 🙂

I find that dual install method a bit awkard though, especially after I found out that whatever order is specified in $PATH, bash seems to always and blindly complete unqualified commands like `perl -v` `to /sbin/perl -v`, therefore bypassing my $PATH order !! (although `which perl` rightfully says `/usr/local/bin/perl` ..) !!
Not sure which mechanism is acting there, but this leaves a bad taste in my mouth.

If you see a better way, let me know.

Else yes, and in support of LAMP on Void Linux https://gist.github.com/adnan360/045d1e4c7619a1e1a9e779d6d35cca92, it would be good to modify our Perl packages with either `-Uusethreads` for no thread at all, or both `-Duseithreads -Dusemultiplicity`, so that it is easy to use mod_perl, and its persistent `ModPerl::Registry / ModPerl::RegistryPrefork` feature for performance.