tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Importing libraries for the kernel



On Thu, Dec 13, 2018 at 2:12 AM Greg Troxel <gdt%lexort.com@localhost> wrote:
>
> maya%netbsd.org@localhost writes:
>
> > I don't expect there to be any problems with the ISC license. It's the
> > preferred license for OpenBSD and we use a lot of their code (it's
> > everywhere in sys/dev/)
>
> Agreed that the license is ok.
>
> > external, as I understand it, means "please upstream your changes, and
> > avoid unnecessary local changes".
>
> Agreed.
>
> And also that we have a plan/expectation of tracking changes and
> improvements that upstream makes.  Code that is not in external more or
> less implies that we are the maintainer.  For these libraries, my
> expectation is that they are being actively maintained and that we will
> want to update to newer upstream versions from time to time.

I think libsodium matches the case.  The project is active and we should
track the updates.

OTOH for libb2 (blake2s), we need just two files (.h and .c) and those
seems to be a reference implementation of the algorithm and unlikely
to update, at least, frequently.  So just copying the files may work.

Note that it's not to say that I don't want to do the formal process
(because I've already done the task in my local changes).  I just don't
want to increase unnecessary files in the repository if possible (and
if preferable).

Anyway thank you for suggestions!
  ozaki-r


Home | Main Index | Thread Index | Old Index