Why not optimize the file scanning and file copy code such that:
1. during the initial profile scan, acquire the information necessary
to be able to group the actions into two groups:
file deletions, and file copies - then
2. perform the file deletions *first*, then
3. perform all file copies in order of file-size, smallest to largest.
This completely and totally eliminates the need for an option for what to do if a disk full error is encountered for any profile - the program would know that none of the other files will fit until the error is corrected, so it fails with a fatal error and moves on to the next profile (which may be copying files to a totally different location).
1. during the initial profile scan, acquire the information necessary
to be able to group the actions into two groups:
file deletions, and file copies - then
2. perform the file deletions *first*, then
3. perform all file copies in order of file-size, smallest to largest.
This completely and totally eliminates the need for an option for what to do if a disk full error is encountered for any profile - the program would know that none of the other files will fit until the error is corrected, so it fails with a fatal error and moves on to the next profile (which may be copying files to a totally different location).