Date: Thu, 15 Jan 2004 10:25:32 -0800 From: David Schultz <das@FreeBSD.ORG> To: Tim Kientzle <kientzle@acm.org> Cc: freebsd-arch@FreeBSD.ORG Subject: Re: Request for Comments: libarchive, bsdtar Message-ID: <20040115182532.GA26149@VARK.homeunix.com> In-Reply-To: <4004D445.7020205@acm.org> References: <4004D445.7020205@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 13, 2004, Tim Kientzle wrote: > Request for Comments: libarchive, bsdtar > > PROPOSAL > > Add "libarchive" to the tree, prepare to change the system > tar command to "bsdtar" once it is sufficiently stable. Nice! I'm sure this will be immensely useful when finished. I have a few pseudorandom comments: - Have you considered extending the API such that it is able to efficiently support random access archive formats? This would also be useful for sequential access formats such as tar(5) because the library could be extended to generate an in-core hash index for the archive on the fly, speeding up multiple lookups. Java's ZIP interface does this, for instance. - The HTTP and FTP support in libarchive(3) seems superfluous. Applications that need this feature can use libfetch(3) directly. (I realize that similar libraries such as libcomprex(3) do this, but that doesn't necessarily make it right.) - When this is done, I'm wondering what potential impact it might have on sysinstall and the archive format it uses... (not that I really want to reopen that bikeshed)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040115182532.GA26149>