gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: patch-log sizes


From: Tupshin Harper
Subject: Re: [Gnu-arch-users] Re: patch-log sizes
Date: Wed, 17 Dec 2003 12:17:04 -0800
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4

Tom Lord wrote:

   > From: Tupshin Harper <address@hidden>

> This reminds me of a question that I've been meaning to ask for some > time. Is there a strong reason why it makes sense for arch to store > files in compressed tars as opposed to storing compressed files in > uncompressed tars? Specifically, the difference between a .tgz > containing many .txt files vs a .tar containg many .txt.gz files. > (Extensions used just to illustrate the fundamental nature of the files > in question). Presumably compression ratios would be somewhat less, but > accessing a limited subset of the files in the tar would be *much* cheaper.

   > Any thoughts? What am I missing?

Revision libraries are a better way to provide cheap access to
individual source file trees.

Remember that most revisions are stored as changesets so that the .tgz
is going to contain diffs, not individual source files.   Are you
really sure you want to optimize access to those diffs?
Absent any substantial costs, of course I would. ;-).

(I would guess, (but it is just a guess), that the compression ratios would be "much" less, not "somewhat" less.)

-t

Yeah...on reflection, given the extremely small size of most of the content, you are probably correct. It seems like a bit of a pity, though, that there doesn't appear to be a good, portable, "free", compressed archive format with inexpensive random access.

(does web search and comes up with http://www.nongnu.org/duplicity/new_format.html as an example of somebody in the planning stages of addressing this need, though I disagree with some of his approach)

-Tupshin




reply via email to

[Prev in Thread] Current Thread [Next in Thread]