4 Sep
2010
4 Sep
'10
9:16 a.m.
Hi Dan, 2010/9/2 Dan McGee <dan@archlinux.org>:
This does not remove the MD5 code from our codebase, but it does enable linking against OpenSSL to get their much faster implementation if it is available on whatever platform you are using. At configure-time, we will default to using it if it is available, but this can be easily changed by using the `--with-openssl` or `--without-openssl` arguments to configure.
What about just replacing the current MD5 implementation with the OpenSSL implementation? This would prevent conditional compilation and a direct OpenSSL dependency in libalpm. Jürgen