Raku
"Can't locate Digest/SHA.pm in @INC" on CentOS 6
Zoffix said on IRC: Digest::SHA is core, but centos/redhat/fedora have broken the packaging. You need to install the 'perl-core' package to get a complete perl instlalation: sudo dnf install perl-core
It is not nice to have it fail partway through installation, we should detect the missing module in Configure.pl
I think the situation would be pretty much different now, considering everything has changed in the build system. @samcv can you re-check how things currently are?
I happen to have a window open. It fails much earlier now, thanks to more Fedora lobotomy:
[nick@gcc120 rakudo]$ perl Configure.pl
Can't locate IPC/Cmd.pm in @INC (@INC contains: /home/nick/Perl/rakudo/tools/lib /home/nick/Perl/rakudo/3rdparty/nqp-configure/lib /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /home/nick/Perl/rakudo/3rdparty/nqp-configure/lib/NQP/Macros.pm line 87.
BEGIN failed--compilation aborted at /home/nick/Perl/rakudo/3rdparty/nqp-configure/lib/NQP/Macros.pm line 87.
Compilation failed in require at /home/nick/Perl/rakudo/3rdparty/nqp-configure/lib/NQP/Config.pm line 28.
BEGIN failed--compilation aborted at /home/nick/Perl/rakudo/3rdparty/nqp-configure/lib/NQP/Config.pm line 28.
Compilation failed in require at Configure.pl line 30.
BEGIN failed--compilation aborted at Configure.pl line 30.
Also, this machine is relatively old Fedora. At some point after this version, I think that (finally) Fedora got the memo, and changed things round so that the most obviously named perl package is the full core distro, so at least for human sysamdins picking packages, the most likely choice is to install something useful. However I don't know if the installation default remains this butchered package (just with a "better" name)
@vrurg I don't have any Redhat/Fedora systems currently, so I can't test this, sadly.
What is needed to test out this issue? I have Fedora 32 and was able to e.g. build releases just fine.
@Altai-man as far as I understand the best test is a CI using an image of a weird distro. Though to my view "weird" is rather polite word for the case because separation of core modules from the perl itself is beyond any reasons.
And I don't see what else can be done to handle such situation beside of a big expressive error message asking to pull the required modules. Though, to be frank, I have once implemented autoinstall of dependencies for Foswiki using cpanm...
as far as I understand the best test is a CI using an image of a weird distro
Weird distro be what? Fedora from 2018 or?
If it separates the core modules from the binary without installing them as dependencies – then, yes! :)