[Mesa-dev] [PATCH] util: import sha1 implementation from OpenBSD

[Steven Newbury]

On Wed, 2017-01-18 at 20:43 +1100, Timothy Arceri wrote:
> On Wed, 2017-01-18 at 08:30 +0000, Steven Newbury wrote
[SNIP]
> > 
> > Why not leave in a build time option for whichever is the fastest
> > (non-
> > OpenSSL) external SHA1 implementation but default or fallback to
> > whatever gets pulled into the tree?
> 
> Because OpenSSL is not the only implementation used by games, leaving
> this option in just leaves room for future problems. I'm all for
> importing an implementation I just wanted to be sure we make a good
> choice as we will likely be stuck with it for a long time.
> 
Okay, fair enough.  Pressure needs to be kept on game producers not to
statically link system libraries though.  SHA1 might be relatively
unimportant, but it's part of a trend of importing/bundling code
instead of using shared libraries that many projects find themselves
pushed into to work around yet other projects doing the same thing. 
Mesa has always been quite good in this regard.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20170118/babb8314/attachment.sig>