Huge count of update files

Hi

I have an software with every week releases. I'm using wyUpdate for building new packages. How I get a problem with many-many files that created every time while publishing.

Let's assume I have 10 versions. In that case I have 1-2, 1-3, 1-4, ... 9->10 files. Is it any options to build incremental updates 1->2, 2->3, ... 9->10 ? So If user has 6 version he will download at the first 7-th versions diff, then 8-th versions diff and so on.

Hope I've clearly explain problem with many version based software.

Is it any options to build incremental updates 1->2, 2->3, ... 9->10 ? So If user has 6 version he will download at the first 7-th versions diff, then 8-th versions diff and so on.

Not with wyBuild 2.6.x. It's coming. (No ETA yet).

Too sad. How I have around 100gb updates files for app about 35mb in zipped mode. 🤣

Two quick questions.

1. When 2.6 will be available? I mean this year or later?2. I would like to delete some files to reduce size on the server. If I delete for example 1->3, 1->4, 2->4 files and leave only 1->2, 2->3, 3->4 does users with version 1 and 2 correctly upgrade to 4-th version? Is is possible with several downloading, right? For example if user has 1 version he will be upgraded into 2 version. Then to 3. And that to 4. Right?

You can delete any X->Y updates where "Y" is a previous version.

You can delete any X->Y updates where "Y" is a previous version.

What's about Wys file? Does it keep some info about published files?

Just one suggestion - please change your format on xml. We keep files on source control system and binary settings looks like a mesh.

What's about Wys file? Does it keep some info about published files?

Yes.

Just one suggestion - please change your format on xml. We keep files on source control system and binary settings looks like a mesh.

We've considered it. We might do it (there are trade-offs -- search the forum, this has been discussed many times).