On Mon, 27 Aug 2018 16:17:31 -0400, Eli Schwartz wrote: > Huh, and we never documented that we supported it in the first place. :/
It did show up in the NEWS file, but no where else. > No wonder we didn't notice that this would break, and, equally, no > wonder users didn't hit this in the 2.5 years since 5.0.0 was tagged... > > But, if we're going to support whirlpool then that means, going against > the original intent of the patch which broke this, that we now need the > openssl command-line tool even if built --with-crypto=nettle, because it > doesn't look like nettle supports whirlpool any more than base64. It should only need the openssl command-line tool if it's actually going to use whirlpool for a given PKGBUILD (i.e., and optdepend at best). -- Happy hacking, ~ Luke Shumaker
