Comment 1 for bug 1619362

The image is created as a sparse file, so does not occupy 4G on disk. We use xz for compression everywhere, so the sparseness is preserved when decompressing. What is the use case for which the pre expanded filesystem causes a problem? Note that even dd has sparse handling, though this was unfamiliar to me until recently, so it's possible even to ensure efficiency when writing out to an sd card.

I'm not saying we can't make this change, if first boot resizing is preferred; I'd just like to be sure we understand what is actually impacted.