No. wyUpdate will see that the file is missing and quits looking. It only downloads the "all.to.x" file if a file fails to patch from the "X.to.latest" update file.
Why do you want this?
Let's say I have application version 1.0. Then I release application version 1.1 and publish .wyu files to server.
Client application version 1.0 detects new version and launches update process. This update then checks for file 1.0.to1.1.wyu on server. What if this file is missing on server and only all.to.1.1.wyu file is available.
Would update be possible?
No. wyUpdate will see that the file is missing and quits looking. It only downloads the "all.to.x" file if a file fails to patch from the "X.to.latest" update file.
Why do you want this?
Update process would be more robust.
For example, with this feature you could release version 1.0 and after feew weeks you make minor change in code but do not want to change version. I would rebuild application and create new setup for version 1.0.
When I create version 1.1 of application I would manually delete 1.0.to1.1.wyu file which would enable both applications with version 1.0 to update.
With this change you would not break standard behaviour (and I think it would be very useful for some users, including me).
What do you think?
What do you think?
Unless I'm misunderstanding you, this idea encourages bad practices and can cause lots of problems. For instance, why do you want to release a new version without at least updating the revision number (See version numbers)?
I'm not sure I understand why you don't just release a new version with the minor changes? If the changes are small, then the update patch will be similarly small.