From owner-freebsd-current@FreeBSD.ORG Sat Apr 24 15:06:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3A9116A4CE; Sat, 24 Apr 2004 15:06:10 -0700 (PDT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCD5E43D5D; Sat, 24 Apr 2004 15:06:10 -0700 (PDT) (envelope-from tim@kientzle.com) Received: from kientzle.com (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id i3OM6A90098310; Sat, 24 Apr 2004 15:06:10 -0700 (PDT) (envelope-from tim@kientzle.com) Message-ID: <408AE4D1.4060609@kientzle.com> Date: Sat, 24 Apr 2004 15:06:09 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Lewis References: <200404242152.i3OLq87E057024@gw.catspoiler.org> In-Reply-To: <200404242152.i3OLq87E057024@gw.catspoiler.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: richardcoleman@mindspring.com cc: current@FreeBSD.org Subject: Re: Amanda, bsdtar, and libarchive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Apr 2004 22:06:11 -0000 Don Lewis wrote: > On 24 Apr, Tim Kientzle wrote: > >>If you want reasonably accurate estimates without reading the >>file data, you could ... build some sort of "size estimate" capability into >>libarchive ... > > There are three variations on the archive size estimate: > Fast and exact > Fast and approximate > Slow and exact You can already do the last one with libarchive; just register an output function that counts the bytes but doesn't do anything. Done. "Fast and exact" is simply not possible in general, so I don't think I would bother with that option at all. Incorporating some sort of estimator into the API does sound like a good idea. I'll have to think about it some to see if I can figure out a good way to do that. Thanks for the feedback, Tim