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

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

Re: [Gnu-arch-users] Re: ViewARCH-0.0.2


From: Tez Kamihira
Subject: Re: [Gnu-arch-users] Re: ViewARCH-0.0.2
Date: Tue, 09 Sep 2003 08:48:58 +0900 (JST)

Hi,

On Mon, 08 Sep 2003 08:14:00 -0500, John Goerzen <address@hidden> said:
> 
> 1. What exactly is the relationship between ViewARCH and ViewCVS?  It
> seems to install *both* scripts and config files for each.
>

ViewARCH is a _normal_ CVS tracking branch of ViewCVS. If something occurrs in
ViewCVS's core part, I can get it by executing "cvs up" in the top directory.
I can do "cvs diff" anytime, too.

But ViewARCH is also a typical "GNU arch" project. You can do
"tla what-changed --diffs" and everything that GNU arch can do

My aim is to make a typical/practical CVS->GNU arch migration project,
as well as to provide light/thin repository browser for GNU arch.

"viewcvs.cgi" and "viewcvs.conf" have no meaning when installing ViewARCH.
If many people are confused, I can cleanup install script and remove them.


>
> 2. How large will that cache get?  Does it actually cache every rev of
> an archive?  Can the size be configured at all?
> 
> If it does cache every rev, I'm looking at a situation in which it
> could easily consume gigabytes of space.
>

no. of course. :)
Almost everything you can see is virtual. Don't worry.

When

    changeset_size(n) ... uncompressed data size of changeset-n
    binary_size(n)    ... uncompressed data size of total _binary data_ size
                              in changeset-n
    current_rev       ... current newest revision number
    working_directory_size(n) ... working directory size of pure revision-n

then, very roughly,

    total_cache_size = 0
    for i = 0 to current_rev
        total_cache_size += ( changeset_size(i) - binary_size(i) )
    total_cache_size += working_directory_size(current_rev)

    For every version, total_cache_size is what you want.

But technically, working_directory_size(current_rev) is redundant.
To erase it, I have to compute every delta of my cache from GNU arch's
changeset directly. ( In ViewARCH-0.0.2, I still rely on the above working
directory )

And that will be my goal in ViewARCH-0.0.3 (or won't).


      - Tez




reply via email to

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