On Thu, Sep 1, 2011 at 11:20 AM, Dmitry Chestnykh
<dmi...@codingrobots.com>wrote:
> > but it's not clear the openssl code is always a win... I'm not sure
> whether or not it's a good idea to try to determine at run time which to use
> (since the check overhead has to be measurable after all).
>
> Yes, let's leave it as it is.
There are cases where OpenSSL is clearly not a win. Not for speed, but for
ease of deployment. My first use of fossil came about because I couldn't
convince python to build with any of the openssl modules installed on an old
version of Solaris - so mercurial flat wouldn't work, even though I didn't
need SSL.
Fossil not using openssl meant that fixing this was a matter of turning off
ssl support.
Given that one of fossil's selling points is ease of installation, including
having no external dependencies. Let's not changethat.
<mike
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
