Closed ashb closed 11 years ago
I'm guessing you mean for get and put operations?
get is easy - can just stat() the local path. put is harder because it'd have to check if the remote file existed on S3 first.
Oh also I notice we've already got -f for "config file". I wonder about turning that to
'C|config=s'
thus leaving -f for the more traditional --force meaning
Was thinking for remote operations, yeah (so put uncat etc.)
Changing to -C makes sense - for for it
Just for sanity sake I'd prefer it if it wouldn't overwrite existing files without a -f mode.
If it doesn't make sense for all applications I'd like a --no-overwrite that I could use for this script.