Hi Niels, Most of the arguments in this and previous bugs are anecdotal. It would be helpful to provide a concrete analysis of the disk space savings that compression provides, and whether it is a reasonable default. There is a discussion about KDE debug symbols requiring 10Gi of disk space a decade ago, but not what the original compressed size was, for example... Would you be able to research some representative slice of popular packages that would be affected by the policy change (at least 10) and share the on-disk sizes with compression vs. without? Personally, I think if there is not much difference in size, it would make sense to not compress as the default. If there are orders of magnitude in difference, the status quo probably still makes sense, as it does provide benefits. Matthias, You and the original report mention "tooling issues". Can you please provide some examples of tools that do not currently support working with compressed symbols and the resulting effects on developer workflow? Thanks, - e
Attachment:
signature.asc
Description: PGP signature