There should also be a 'duplicity list-backends' that will show available backends and their protocol strings, something like: ftpbackend ftp:// sshbackend ssh:// scp:// ...and so on...
-- Backend imports should be made optional https://bugs.launchpad.net/bugs/394757 You received this bug notification because you are a member of duplicity-team, which is subscribed to duplicity. Status in duplicity - Bandwidth Efficient Encrypted Backup: Confirmed Bug description: Certain backends require other modules, ncftp for FTP, sftp for SSH, etc.. If the user is not going to be using these modules, it should not be a requirement to have them on the system. I propose that we surround all backend imports with a try/except and that all modules should check requirements at import time prior to calling register_backend. If a backend fails to load, the default should be silence, however a verbosity of INFO or better should show why. _______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
