From owner-freebsd-hackers  Mon Aug 25 20:46:40 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id UAA02851
          for hackers-outgoing; Mon, 25 Aug 1997 20:46:40 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA02843
          for <freebsd-hackers@freebsd.org>; Mon, 25 Aug 1997 20:46:36 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id UAA00346; Mon, 25 Aug 1997 20:39:15 -0700 (PDT)
To: Mike Smith <mike@smith.net.au>
cc: david@sparks.net, Alexander Indenbaum <baum@actcom.co.il>,
        A Joseph Koshy <koshy@india.hp.com>, freebsd-hackers@freebsd.org
Subject: Re: Checking the integrity of system files 
In-reply-to: Your message of "Tue, 26 Aug 1997 12:52:30 +0930."
             <199708260322.MAA00584@word.smith.net.au> 
Date: Mon, 25 Aug 1997 20:39:15 -0700
Message-ID: <342.872566755@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> It uses the 'gdbm' library, which is GPL'd (note _NOT_ LGPL), and it 
> still doesn't provide the level of smart integration we want/need.

And it uses a non-standard archive format, something which many people
praise the current installation tools for not doing.  It can come in
handy to be able to disassemble a package file on some other system
and inspect it easily.

					Jordan