svn commit: r337936 - in head/sys/contrib/libsodium: . builds builds/msvc builds/msvc/build builds/msvc/properties builds/msvc/vs2010 builds/msvc/vs2010/libsodium builds/msvc/vs2012 builds/msvc/vs2...

[John Baldwin]

On 8/17/18 1:23 AM, Conrad Meyer wrote:
> Author: cem
> Date: Fri Aug 17 00:23:50 2018
> New Revision: 337936
> URL: https://svnweb.freebsd.org/changeset/base/337936
> 
> Log:
>   Bring in libsodium to sys/contrib
>   
>   Bring in https://github.com/jedisct1/libsodium at
>   461ac93b260b91db8ad957f5a576860e3e9c88a1 (August 7, 2018), unmodified.
>   
>   libsodium is derived from Daniel J. Bernstein et al.'s 2011 NaCl
>   ("Networking and Cryptography Library," pronounced "salt") software library.
>   At the risk of oversimplifying, libsodium primarily exists to make it easier
>   to use NaCl.  NaCl and libsodium provide high quality implementations of a
>   number of useful cryptographic concepts (as well as the underlying
>   primitics) seeing some adoption in newer network protocols.
>   
>   I considered but dismissed cleaning up the directory hierarchy and
>   discarding artifacts of other build systems in favor of remaining close to
>   upstream (and easing future updates).
>   
>   Nothing is integrated into the build system yet, so in that sense, no
>   functional change.

Can you import this into the vendor area and then do a bootstrap of
mergeinfo to sys/contrib?  This permits future updates to use svn to
merge instead of doing it by hand.  It also permits future imports to
be done by other developers following our standard, documented process
for working with third-party code.

-- 
John Baldwin