Hi Helen,
> right, the binary package is not called rust-bat but the source package is
> [1].
> Can lintian check for the source package name? (also not sure if it is
> a good idea).
It could but, alas, the I think the "package exception" mechanism
regarding the binaries/embedded-libs data file appears to use the
binary package name...
> Do you think it would be a good idea to rename the binary package?
Just to silence this Lintian warning? That would seem like extreme
overkill to me! Regarding finding another string that is present in.
libyaml and not in rust-yaml-rust, do you have any suggestion at this
point?
> Just a question regarding how lintian works: one thing that confused me is
> that
> bat doesn't depend on rust-yaml-rust directly, it depends on rust-syntect
> which
> depends on rust-yaml-rust. So I was wondering why I didn't get this
> error in lintian when building rust-syntect.
I have not checked but isn't the question/issue around Rust embedding
the code of the library in question rather separate to the chain of
Debian-level dependencies. In other words, isn't this apparent
perculiarity explained by that bat embeds the rust-yaml-rust bit of
YAML parsing/generation code whilst that bit of rust-yaml-rust isn't
used in rust-syntect and thus is not embedded?
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
