[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Duplicity-talk] Duplicity-talk Digest, Vol 247, Issue 1
From: |
Wolfgang Rohdewald |
Subject: |
Re: [Duplicity-talk] Duplicity-talk Digest, Vol 247, Issue 1 |
Date: |
Wed, 23 Jan 2019 13:28:41 +0100 |
On Mi, 2019-01-23 at 10:36 +0000, Aaron via Duplicity-talk wrote:
> Hello all,
>
> I have been thinking for a while that we need something more easily machine
> parseable -- even if just to aggregate information from multiple duplicity
> runs. My plan for it was to add a new --json flag or similar that spits out
> JSON or whatever can be easily consumed by other applications through
> familiar libraries but can also be extended.
>
> From memory this will not be straightforward, as the current code spits
> things out in various places, rather than collating summary information and
> formatting it in one place.
I am dreaming of a local installation of readthedocs and a converter which
converts
duply output into something like the readthedocs build process logs
So - something more parseable like json would definitively be very welcome.
--
Wolfgang