When implementing a dynamic check_digest around hook it is called up to 3 times, depending on the value of Digest attributes check_fetch and check_download. I've seen that $build->extract does most of the rule enforcement of download_rule and thought this could benefit from a change against some low effort subversion such as the around_hook below. By the build stage there shouldn't be any opportunity to update the meta_prop->{digest}
use alienfile;
share {
plugin Digest => {'*' => [SHA256 => 'x' x 64]};
meta->around_hook(check_digest => sub { return 1; });
};
When implementing a dynamic
check_digestaround hook it is called up to 3 times, depending on the value of Digest attributescheck_fetchandcheck_download. I've seen that$build->extractdoes most of the rule enforcement of download_rule and thought this could benefit from a change against some low effort subversion such as the around_hook below. By the build stage there shouldn't be any opportunity to update themeta_prop->{digest}