The package list comparison results in a bit ahead of unsable package version, not many about 20 packages only. But all version set by names are the same. So slightly difference in image sizes are expected.
du * --bytes --human-readable
3.4G manjaro-kde-21.11-development-unstable-211119-linux515.iso
2.7G manjaro-kde-21.11-development-unstable-minimal-211119-linux515.iso
du * --bytes --human-readable
3.7G manjaro-kde-21.2pre1-211119-linux515.iso
3.0G manjaro-kde-21.2pre1-minimal-211119-linux515.iso
or the same but bytes-scaled:
du * --bytes
3575742464 manjaro-kde-21.11-development-unstable-211119-linux515.iso
2873233408 manjaro-kde-21.11-development-unstable-minimal-211119-linux515.iso
du * --bytes
3885817856 manjaro-kde-21.2pre1-211119-linux515.iso
3183362048 manjaro-kde-21.2pre1-minimal-211119-linux515.iso
Slightly. But not so huge like that.
May be some compression was not applied or applied another method or why?
du * --bytes --human-readable
3.6G manjaro-kde-21.11-development-unstable-211120-linux515.iso
3.0G manjaro-kde-21.11-development-unstable-minimal-211120-linux515.iso
or bytes-presented
du * --bytes
3863400448 manjaro-kde-21.11-development-unstable-211120-linux515.iso
3160891392 manjaro-kde-21.11-development-unstable-minimal-211120-linux515.iso
Now I see almost no size difference between today’s unstable and yesterdays’s stable ISO images. unstable ISO “inherits” that +300 MB from it. But what exactly became bigger and why?
What package got changes if to compare unstable from yesterday and unstable from today:
Yeah, previously I also though that, but I compared packages list:
typical stable with typical unstable,
minimal stable with minimal unstable.
Comparison result goes like this:
“set” I meant list of packages - packages set.
So it is not the case.
I did not mention that today, but I stays in context of initial post: if to compare yesterday’s unstable to today’s unstable then I see exactly the same set of packages, no one was removed or added. Only those 9 packages changed their versions.
I did that comparison by *.pkg files comparing, which located in the same post with ISO images.
Dan, if you daily build ARM images, then recent (from yesterday evening or today) ARM ISO image versions did not get that comparable size increase? I wonder if it is some global settings involved, under which ISO imaged of all architectures builds (if such settings exists).
I thought that packages inside of ISOs are the same as mirror servers has: they are not pre-installed inside of image (only some core system packages installed to start to run the image), but while ISO starts that packages got unpacked, installed into RAM and run.
So, installed size: 580 MiB
Download size: 275 MiB
But all the packages already was inside of earlier lighter ISOs, so download size of 275 MiB could not cover that additional ~300MiB.
If they was pre-installed inside of ISO: switch from next version gave + 300 MiB? So their size now 580 MiB and a day before was 580 - 300 = 280 MiB, so the size increased twice? Can’t believe that.