No. The best way to do what you want to do is to only have a single version in wyBuild. Then simply rename the version in wyBuild on every release of your app. This will force wyUpdate to use "dumb updating" instead of the "smart patching". In other words, when you have only a single version in wyBuild you're forcing wyUpdate to just dumbly copy files overwriting any existing files.
best strategy to execute catch-all updates
csuserHere's the problem. I am trying to use wyUpdate to handle out daily builds. Which happen daily, sometimes several times a day. Application is structured in a way that version 0 is just a skeleton, and wyBuild is used to actually deploy the application. Say, I am releasing version 1000. I found out that I need to create update myapp.0.to.1000 and myapp.all.to.1000 at the same time. There's almost no difference. I would rather force application to use 'myapp.all.to.1000' if update 'specificversion.to.1000' is not found, but somehow it does not happen automatically, app just stops if t does not see specific update file and does not fall back to 'catch-all' update. Is it possible to force it to catch-all update in such scenario?
csuserWow, that works perfectly, thanks! One thing though is that I have to create two patches every time, "0.to.X" and "all.to.X". This is way better than maintaining quadratic number of updates, but I still wonder if there a way to reduce it to one patch file only?