Date: Mon, 9 Jul 2001 17:36:29 -0400 (EDT) From: Keith Bostic <bostic@sleepycat.com> To: mi@aldan.algebra.com Cc: current@FreeBSD.org, msmith@FreeBSD.org, wes@softweyr.com Subject: Re: nvi maintainer? Message-ID: <200107092136.f69LaTx27514@abyssinian.sleepycat.com>
next in thread | raw e-mail | index | archive | help
>> Just to be clear -- they could link against it using the same, >> standard functionality that FreeBSD uses. They couldn't link against >> it and use all the additional features/functionality. > > So we'll have to document, which functions it is Ok to call and which > arguments/flags can and can not be passed to them. Brrrgh... As a system distributor in a previous life, "Brrrgh" indeed. :-) The way we've done this for previous systems is not try and document how it can be called, but only permit use *through* the system's library, that is, use it via getpwent(), the libc network functions and so on. >> My guess is that your answer remains the same -- and, that's cool, I'm >> used to losing this argument, I do so about twice a year. :-) Just >> wanted to be clear. > > Well, can someone comment on the useability of gdbm? I know, it has dbm > and ndbm compatibility "mode" and a less restrictive license. Should we > switch over to it? This isn't necessary. The *current* FreeBSD libc Berkeley DB sources are completely safe -- they're under a UC Regents copyright notice. This discussion is only regarding the possibility of making the Berkeley DB 3.X functionality available to the FreeBSD community and its customers. Regards, --keith =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Keith Bostic Sleepycat Software Inc. bostic@sleepycat.com 118 Tower Rd. +1-781-259-3139 Lincoln, MA 01773 http://www.sleepycat.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200107092136.f69LaTx27514>