Problem: File::Bundled is outdated and needs to be replaced. But
%?RESOURCES fails to handle situations where the lib name cannot
be guessed (given ssl it would need to produce libssl.so and
ssleay.dll AND libeay.dll. This leaves windows openssl-less
Solution: Replace File::Bundled with %?RESOURCES anyway. The ugly
part of this means non-windows users still have to store the .dll
files even though they will never be used. This is accomplished
by not using the actual %?RESOURCES api internally on anything
except windows (see: OpenSSL::NativeLib.pm6). Its better to
support openssl on windows than to wait for other possible
fixes in rakudo itself, but in the future this should be
replaced
Bonus: Build.PM is no longer needed. So dependencies on panda
and Shell::Command can be dropped (in addition to File::Bundled)
Problem: File::Bundled is outdated and needs to be replaced. But %?RESOURCES fails to handle situations where the lib name cannot be guessed (given ssl it would need to produce libssl.so and ssleay.dll AND libeay.dll. This leaves windows openssl-less
Solution: Replace File::Bundled with %?RESOURCES anyway. The ugly part of this means non-windows users still have to store the .dll files even though they will never be used. This is accomplished by not using the actual %?RESOURCES api internally on anything except windows (see: OpenSSL::NativeLib.pm6). Its better to support openssl on windows than to wait for other possible fixes in rakudo itself, but in the future this should be replaced
Bonus: Build.PM is no longer needed. So dependencies on panda and Shell::Command can be dropped (in addition to File::Bundled)