Re: [Duplicity-talk] Duplicity-talk Digest, Vol 184, Issue 1

[Arjun Krishnan]

Hi Aaron

Thanks for the outline, I'm somewhere near DirDelta, where its putting the tar file together

and splitting up the volumes.

Im slowly reading the code like I would read a paper, to figure 

out how the different pieces fit together. Its very clean and readable! 

Arjun

On Mon, Jun 5, 2017 at 10:00 AM, <address@hidden> wrote:

Send Duplicity-talk mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.nongnu.org/mailman/listinfo/duplicity-talk
or, via email, send a message with subject or body 'help' to
        address@hiddenorg

You can reach the person managing the list at
        address@hiddenorg

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Duplicity-talk digest..."


Today's Topics:

   1. Re: Following up on an extended attributes question (Aaron)


----------------------------------------------------------------------

Message: 1
Date: Sun, 4 Jun 2017 22:53:11 +0100
From: Aaron <address@hidden>
To: address@hidden
Subject: Re: [Duplicity-talk] Following up on an extended attributes
        question
Message-ID: <fc5d27d2-9426-4b33-a6d9-address@hiddennz>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

Hello Arjun,

On 30/05/17 12:27, Kenneth Loafman via Duplicity-talk wrote:
> Hi Arjun,
>
> Glad you're willing to help.  The best (only) formal docs we have are
> at readthedocs <https://duplicity.readthedocs.io/en/latest/>, or in
> the docs directory, but those are incomplete.
In the hope of saving you a little time figuring out where to dive in,
an extremely quick overview of the code base, largely from memory (so
don't take as gospel) and assuming a full backup to keep it simple:
1. Start in bin/duplicity main()
2. Process commandline arguments in duplicity/commandline ProcessCommandLine
2.a. parse_cmdline_options() does what you would expect, though watch
the globals.
2.b. Note the set_selection(), which doesn't really belong here, but
triggers all the selection code in duplicity/selection (walking over the
filesystem to see if files match the glob patterns etc that people have
passed as --include/--exclude options).
3. bin/duplicity do_backup() to decide what type of backup (full,
restore etc)
4. I believe bin/duplicity full_backup() then kicks off all the writing
to signature and archive files, using the various backends.

Hopefully that helps. Anyone else feel free to jump in if I have
anything wrong or misleading.

Kind regards,

Aaron


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nongnu.org/archive/html/duplicity-talk/attachments/20170604/232035c5/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk


------------------------------

End of Duplicity-talk Digest, Vol 184, Issue 1
**********************************************