Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: Ivan Shmakov <oneingray@gmail.com>
Newsgroups: comp.unix.misc,comp.software.testing,comp.sources.testers
Subject: Re: filesystem content tracking
Date: Thu, 22 Mar 2012 11:41:12 +0700
Organization: Aioe.org NNTP Server
Lines: 53
Message-ID: <86fwd1xn6f.fsf@gray.siamics.net>
References: <86aa3j9quj.fsf@gray.siamics.net> <86fwd43lai.fsf@gray.siamics.net>
NNTP-Posting-Host: FtDGZaUx6k7Bzdiv4MgYAg.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@aioe.org
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)
X-Notice: Filtered by postfilter v. 0.8.2
Cancel-Lock: sha1:5+th/BqTcYJdLd/byLcBhODHvF0=
Xref: csiph.com comp.unix.misc:70 comp.software.testing:171 comp.sources.testers:7

>>>>> Ivan Shmakov <oneingray@gmail.com> writes:
>>>>> Ivan Shmakov <oneingray@gmail.com> writes:

[...]

 >> Unfortunately, the use of the previously recorded sessions is not
 >> implemented at this moment, so I don't have the space requirements
 >> for the "incremental update" case at hand, but I expect them to be
 >> times lower than those for the SQLite-based version.  Combined with
 >> the ability to easily compress or move away the older sessions, I
 >> hope this may finally get the tool to a usable and useful state.

 > And here they are:

[...]

	One thing to note, however, is that there's no proper support
	for "incrementally updating" a session which is in turn an
	"incremental update."  IOW, if one records session A, and then
	records an "update" B, it's not currently possible to use both A
	and B combined as the basis for a further update C.

	As a work-around, the C session may be recorded as an update to
	A instead.  (Thus getting all the files changed or added since A
	rehashed for both B, C, and all the subsequent sessions based on
	A.)  Like:

    A --> B --> C --> D         currently not implemented;

    A                           possible, though not as time and space
    |--> B                      efficient.
    |--> C
    `--> D

	The support for such a mode of operation shouldn't be that hard
	to implement, but I wish to make some clean-ups to the code
	before that.  (In particular: split the code into separate Perl
	modules, commit the "dump" utility source to the Git repository,
	provide a CPAN package, allow for a-times and other not that
	important metadata to be omitted from the record.)

 >> (For anyone wishing to try this version, its sources could also be
 >> found at [1, 2], under the fccs-2012-03-asn.1 branch.)

 > ... Though I'm yet to upload the recent changes there.

	Done.

 >> [1] http://gray.am-1.org/~ivan/archives/git/gitweb.cgi?p=fc-2012.git
 >> [2] http://gray.am-1.org/~ivan/archives/git/fc-2012.git/

-- 
FSF associate member #7257