Reduce IUK size
This is about researching low-hanging fruits to reduce the size of our IUKs in order to be nicer to users with not very fast Internet connection. Regarding increased memory consumption caused by the "single SquashFS diff" idea, another approach (#6876) will solve the problem.
- apply the
/var/lib/dkms/during the build, then remove the dkms bits from
To evaluate the impact of these ideas:
- Fork the tag for Tails version N, apply the aforementioned tricks. Build an ISO.
- Do the same for Tails version N+1.
- Build the IUK from N to N+1 using these ISOs.
- Compare the size of the IUK you've built with the size of the IUK we've published from N to N+1.
This is related to #15281 (1BigIUK) because of the larger IUKs. Once we have it it really seems worth at least picking the low-hanging fruit among size optimizations.
Yes, maybe… but the marginal benefit (relative to the total upgrade download time) brought by such optimizations will actually be lower once IUKs get bigger. So I guess it could be worth giving a quick try to the low-hanging fruits I've identified on the subtasks and check how much space (and thus download time) we would save, before even evaluating whether these tricks break anything we care about. Now, no big deal if we don't do it IMO.
- Target version deleted (
This would be nice, but technically it's not on our roadmap.
In a build of current devel branch (Buster):
- Compressed with tar+bz2 together,
/var/lib/dpkg/infoare 4.2M large, so best case, we'll be saving a few MB on each IUK.
So implementing our current best ideas would definitely be nice, but that won't improve UX much.
Now, if there are other low-hanging fruits we did not spot, that would impact the IUK size substantially, then it would be a completely different story!