From owner-freebsd-current Tue Jul 10 5:22:51 2001 Delivered-To: freebsd-current@freebsd.org Received: from abyssinian.sleepycat.com (abyssinian.sleepycat.com [199.103.241.218]) by hub.freebsd.org (Postfix) with ESMTP id 6529A37B40F; Tue, 10 Jul 2001 05:22:36 -0700 (PDT) (envelope-from bostic@abyssinian.sleepycat.com) Received: (from bostic@localhost) by abyssinian.sleepycat.com (8.10.1/8.10.1) id f6ACMZX00452; Tue, 10 Jul 2001 08:22:35 -0400 (EDT) Date: Tue, 10 Jul 2001 08:22:35 -0400 (EDT) From: Keith Bostic Message-Id: <200107101222.f6ACMZX00452@abyssinian.sleepycat.com> To: mi@aldan.algebra.com Subject: Re: picking a DB (Re: nvi maintainer?) Cc: current@FreeBSD.org, msmith@FreeBSD.org, wes@softweyr.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Well, can you recommend some other alternative? You mentioned db-tests > you created, etc. Did you evaluate any other dbm libraries useable for > us from the licensing perspective? No -- there aren't a lot of choices here, and nothing that is a good enough choice that it's worth rewriting everyone's data to switch. >> Nvi won't require upgrading the library's dbm support. Berkeley DB 3.X >> supports inclusion of multiple DB versions in a single application. >> Nvi's simple solution is to include a copy of DB in the nvi >> distribution. > > Well, may be that's how the nvi application will be distributed, but I > doubt, that's how the nvi part of the FreeBSD will be built... In all > probability, the new nvi will just get hacked to work with dbm-1.85 or > gdbm. Nvi needs some of the features of Berkeley DB 3.X (transactional logging) in order to fix long-standing bugs in the application. 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