[Pkg-rust-maintainers] Bug#942487: Bug#942487: Bug#942487: rust-web-sys: Provides header is more than 256K long and it breaks reprepro...

[Ximin Luo]

Ximin Luo:
> Raphael Hertzog:
>> On Thu, 17 Oct 2019, Ximin Luo wrote:
>>> Control: tags -1 + wontfix
>>
>> This is clearly not acceptable. You can't ignore problems like this one.
>> I saw you already broke debian-installer once with the former packages
>> that overflowed the 16K limit of cdebootstrap. Now it's the turn of
>> reprepro and this one is harder to fix because there are real servers
>> running stable version of reprepro, etc.
>>
>>> The tool's algorithm was suggested by the maintainer of dpkg and has his
>>> blessing. It is partly due to limitations in dpkg, see #901827 for
>>> details.
>>
>> The algorithm is one thing... but the design of your tool is another
>> thing.
>>
>> dpkg has dpkg-shlibdeps to build dependencies based on exported
>> information by various package (through
>> /var/lib/dpkg/info/*.{shlibs,symbols}).
>>
>> cargo should build the same infrastructure, i.e. have a
>> /var/lib/dpkg/info/foo.cargo used by dh-cargo to build the correct
>> dependency.
>>
>> Don't abuse the "Provides" field when you have such a volume of
>> interfaces to document.
>>
> 
> Can you please explain why 256 KB provides field is "abuse"?
> 
> Do you have some concrete suggestions on how to improve the tool to reduce this "abuse"?
> 

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.

So yes, we need a concrete suggestion on improving the tool, rather than wild hyperbole that its output is "abuse".

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.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git