Follow-up Comment #2, bug #25542 (project duplicity):
I was thinking of attempting this but since I'm cutting my teeth on
this and Duplicity seems to have a pretty unique layout for a python
project, I'd love some guidance.
It looks like breaking up the signature file while writing it to the
remote should be mostly a matter of duplicating the relevante bits of
the "while not at_end:" loop logic from
duplicity-bin:275(write_multivol) to the FileobjHooked.to_remote
method at duplicity/dup_temp.py:169(to_remote). Does that sound
correct?
What I'm having a harder time finding in the code is the right place
to hook into for re-assembling split signatures on restore or
inspection of the remote archive. Can anyone offer any pointers on
that?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?25542>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
_______________________________________________
Duplicity-tracker mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/duplicity-tracker
