Counter-intuitive in the sense that a user cannot undo his own backup, unless manually removing it in the terminal using sudo.
It seems odd, because if a user wants to backup his home folder, or a subfolder within his home, then why would he need to run the backup application with root privileges? And once he does make a backup, even as a .tar.gz, he cannot access the files within; not even being able to extract them, unless he does: sudo tar xfvz mybackup.tar.gz
In the IRC channel, you explained the reason behind root privileges for backing up the software list, which is needed for locking the apt cache.
I agree with your solution, to save the backups and the software list with full read/write permissions: -rw-rw-rw-
The newly created folders within the application should also have full read/write permissions. Right now, browsing for the backup destination and creating a new folder within the Backup Tool will create a folder that only root can delete.
Counter-intuitive in the sense that a user cannot undo his own backup, unless manually removing it in the terminal using sudo.
It seems odd, because if a user wants to backup his home folder, or a subfolder within his home, then why would he need to run the backup application with root privileges? And once he does make a backup, even as a .tar.gz, he cannot access the files within; not even being able to extract them, unless he does: sudo tar xfvz mybackup.tar.gz
In the IRC channel, you explained the reason behind root privileges for backing up the software list, which is needed for locking the apt cache.
I agree with your solution, to save the backups and the software list with full read/write permissions: -rw-rw-rw-
The newly created folders within the application should also have full read/write permissions. Right now, browsing for the backup destination and creating a new folder within the Backup Tool will create a folder that only root can delete.