Yes, I'll put this on launchpad. I just put together a patch to implement this scheme. At my plodding pace it will take a while for even rudimentary testing. But in the process I noted that the way duplicity handles filenames, it looks feasible to have mixed new and old style filenames in a backup chain. In my patch, I use a new switch (--alternate-filenames) to direct what kind of filenames to produce, but it was straightforward to rewrite the regexps used to parse filenames to eat either kind. One concession I had to make was to make changes only at the beginning of filenames, so manifests in my scheme have the string "manifest" twice.
- Dave Cottingham
From: "edgar soldin" <address@hidden>
To: "Discussion of the backup program duplicity" <address@hidden>
Sent: Wednesday, April 17, 2013 12:07:54 PM
Subject: Re: [Duplicity-talk] suggested feature to help Amazon Glacier users
On 17.04.2013 16:15, Will McCown wrote:
> for and incremental. I would suggest changing it to:
>
> duplicity-full-signatures.<date>.sigtar.gpg
> duplicity-full-manifest.<date>.gpg
> duplicity-full.<date>vol<n>.difftar.gpg
just to keep completely in the scheme i'd add 'diff' to the difftar as well.
duplicity-full-signatures.<date>.sigtar.gpg
duplicity-full-manifest.<date>.gpg
duplicity-full.diff.<date>vol<n>.difftar.gpg
aside from that, fully agreed. of course there has to be a fallback to the old naming scheme, or even simpler a major version change signalling incompatibility plus a switch to use the old naming scheme.
additionally there was interest in configuring the named prefix (currently 'duplicity') on this list. could be tackled at the same moment then.
could you add a feature request on launchpad, so this will not be forgotten?
..ede/duply.net
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk