Breaking changes for v2

Here is a list of design mistakes in rclone which we'd like to fix at some possible v2.0.

These will involve some backwards incompatibility.

We could possibly mitigate this with a --v2 flag for people to try these in advance.

Note that rclone 1.0 should not selfupgrade to 2.0 unless requested specifically by the user.

Units for SizeSuffix

Currently all SizeSuffix numbers when expressed without a suffix are in kByte and the B suffix was introduces as an awkward workaround for this.

So --min-size 2 sets the minimum size to 2k not 2 bytes.

This was done for backwards compatibility with rsync and is a mistake in retrospect - numbers without a suffix should be in bytes.

Making rclone emit a warning if no suffix is detected might be a good idea.

Creating containers by default

This is specific to bucket based backends like s3, azureblob, gcs etc.

If you try to create a file remote:bucket/file.txt rclone will automatically try to create the container bucket.

This causes no end of problems with people attempting to lock down their buckets and with not quite 100% compatible s3 clones which get the error codes wrong.

Rclone should never create buckets unless specifically asked to with rclone mkdir remote:bucket

Syncing

The syncing has grown a bit untidily over the years. Here are some things to fix

Make empty directories synced by default so --create-empty-src-dirs should be the default
In rclone move --delete-empty-src-dirs should be the default
Others?

rclone

"rsync for cloud storage" - Google Drive, Amazon Drive, S3, Dropbox, Backblaze B2, OneDrive, Swift, Hubic, Cloudfiles, Google Cloud Storage, Yandex Files https://rclone.org

Rclone