Hello!
Here some observations:
- "those lines" links to a 404.
- "grsync should check if enough space is available on the destination
before running": since grsync doesn't necessarily have access to the
destination directory (rsync does) there is no general method of doing
this. It could be done for "local" folders but it would be a trick. Unless
rsync provides a specific functionality that I do not know of.......
- "grsync should ask for confirmation when the option "Delete on the
destination" is activated": we could build a list of options that need
confirmation, currently none does.
- "when user double-click on a .grsync file, a window appears to confirm
which file to open. This may be confusing.": I thought that worked, maybe
the .desktop or whatever gui file needs updating
Cheers!
On Thu, Jan 22, 2015 at 4:08 PM, matsa <matsa@???> wrote:
>
> Hi list, hi Piero,
>
> I'm part of the people working on Tails, a live distribution that aims
> at preserving privacy and anonymity: https://tails.boum.org/.
>
> Tails is actually lacking a backup tool, and Grsync is actually
> my favorite candidate.
>
> Even if Grsync is already suitable, a few potential improvements have
> been listed after testing.
>
> If you want to get involved in the process, you can find notes in the
> blueprint, and especially in this part about Grsync:
> https://tails.boum.org/blueprint/backups/#index5h2
>
> Hope to read you,
> matsa
>
--
Piero Orsoni
orsoni@???
