You are right. I took the liberty of being inaccurate as Juan was. He posted before stating the complete issue with no reponse.
Reasons for not compressing changelogs <4K: - After compression the file is still occupying 1 allocation unit. There is no space saving. - I have 486 machines here where a gzip invocation causes a delay. I prefer small files (and that means most files since most files are small) to be uncompressed. Speed is a major issue on those machines. - debstd generally compresses all files >4K in /usr/doc. Nice and simple. I really wish to keep things simple. There are already exceptions and it gets to be a major issue to maintain those. - The intend of the policy is to guard against changelogs wasting space. debstd's way of dealing with the issue fulfills that intend and it speeds up low resource machines. In article <[EMAIL PROTECTED]> you wrote: : Christoph Lameter <[EMAIL PROTECTED]> writes: : > As you know well by now Juan: debstd compresses changelogs. So : > please state the issue accurately. : Umm, not always it doesn't. If you're going to ask people to be : accurate, please do the same yourself. If the changelog is small it : won't be compressed, unless I'm mistaken or debstd has been fixed : recently. : -- : James -- --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- Please always CC me when replying to posts on mailing lists.
