On Tue, Sep 30, 2025 at 01:32:22PM +0200, Helmut Grohne wrote:
I'm not sure why there is a rustc dependency here. It is versioned, so maybe the version is the important part.
Yes. In Rust, a crate can specify a minimum required version of rust that needs to be used. This is done so that the crate can take advantage of functionality introduced in said version of the compiler. When crates declare this minimum version, we want to express that in the packaging metadata to avoid trying to build with an incorrect version of the compiler.
Generally though rust crates do not depend on a compiler much like C libraries do not depend on a C compiler. For instance, the rust compiler package may be named rustc-web as is happening in some suites. We also don't impose a minimum gccrs version. Can we drop the compiler dependency? Failing that, can we turn it into Breaks: rustc (<< 1.65)? Failing that, can we annotate it with :any?
Looking at how we handle this in the debcargo side, we only express this relationship in the source package, not the binary packages. I can adjust tree-sitter's packaging to do the same. Cheers, -- James (he/him) GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
