Hi Ben,
Yes, callbacks may be easier than parsing rdiff-backup output, but right now rdiff-backup doesn't support callbacks, and doesn't really have a stable API. Aside from the callback issue, I don't see the API being much friendlier than spawning an rdiff-backup process.
If I added them to the code, would you allow me to distribute the resulting code, to call it rdiff-backup, and would you consider merging it with your main tree?
Cheers, Chris. -- _ ___ __ _ / __/ / ,__(_)_ | Chris Wilson <0000 at qwirx.com> - Cambs UK | / (_/ ,\/ _/ /_ \ | Security/C/C++/Java/Perl/SQL/HTML Developer | \ _/_/_/_//_/___/ | We are GNU-free your mind-and your software | _______________________________________________ rdiff-backup-users mailing list at [email protected] http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
