Comment 8 for bug 1367011

Pawel,

There should be no interactivity after issuing a warning. I expect people are using this as part of cron jobs as well as manually. We /could/ detect if it's running from a user's shell but I would much rather avoid all of this complexity. To put it simply, we should warn users about the destructive action they're performing and then continue and overwrite it. I'm also not entirely convinced that this requires anything more than a warning about existing files that may be overwritten and better documentation, especially given that this would be a very sudden backwards incompatible change.