On Thu, 17 Oct 2019, Ximin Luo wrote: > Can you please explain why 256 KB provides field is "abuse"?
Because that's the amount of metadata required for 250 common packages. > Do you have some concrete suggestions on how to improve the tool to reduce > this "abuse"? Yes, I gave you one. > BTW, the tool is run not at build time but to generate the source > package. So it can't use these "foo.cargo" files, because you don't need > to install all of the dependencies in order to use the tool. If you run a tool to generate the source package, you can include whatever call you want during your source package build. i.e. you control debian/rules too. And you can process the source package and/or the binary package built to create those meta-information and also to use the existing meta-information on the system. > It is 2019. If a tool can't handle 256 KB of data, I'd say the tool is > at fault and not the 256 KB of data. You are being arrogant. Replying in the same tone, I would say that the design of your tool suck. Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/