Re: [rdiff-backup-users] The rdiff-backup poll!

[dean gaudet]

On Tue, 20 Dec 2005, Chris Wilson wrote:

> The main issue with supporting Rdiff-backup is the interface to Python (from
> C++). I was wondering if I could/should embed a Python interpreter in my code
> and use that to call rdiff-backup's functions? I would probably also need to
> implement callbacks to report backup progress and errors in an appropriate
> manner for a GUI.

why wouldn't you just spawn the rdiff-backup program?  otherwise you'd be 
dependent on the internal apis remaining stable... which doesn't seem like 
a good choice for your gui or for rdiff-backup development...

progress meters kind of depend on knowing how much there is to be done, 
and rdiff-backup doesn't know that initially at least... because it starts 
transferring data even before it has scanned all the inodes needing 
backup.  but rdiff-backup could probably be easily mod'd to have an option 
to display how many inodes/bytes it had processed so far... just hook in 
where the file-statistics file is written...

-dean