Rakudo recently started emitting deprecation messages when %?RESOURCES was treated like a path string (see https://github.com/rakudo/rakudo/pull/5507). That affects these openssl bindings because a windows-specific hack was using the base file name of a %?RESOURCE entry, which would cause the aforementioned deprecation messages to be emitted. This PR reworks the hack to not depend on any part of the path name.
Rakudo recently started emitting deprecation messages when
%?RESOURCESwas treated like a path string (see https://github.com/rakudo/rakudo/pull/5507). That affects these openssl bindings because a windows-specific hack was using the base file name of a%?RESOURCEentry, which would cause the aforementioned deprecation messages to be emitted. This PR reworks the hack to not depend on any part of the path name.