Raphael Hertzog: > [..] > > It might not be as flexible as the current approach as it might require > rebuilds when the package providing the interface changes, but that's > quite usual in Debian. >
This isn't suitable for Rust, there will be too many rebuilds needed (basically half the ecosystem for every change, which happens 4-5 times a month) and I and I suspect everyone else will stop maintaining Rust packages if we are forced to do this. > [..] > > But reprepro is in wide use and your new package is the first one to > trigger the limit. You can't just ignore the reality, you have to cope > with the fact that we have reprepro users and that we can't deploy > a package with 270K-long Provides header currently. > Who is using reprepro to archive Debian Rust packages? That's the first time I've heard of this. I suspect this is a small number (its popcon [1] is less than that of rustc itself), and that they will be perfectly happy to upgrade to a fixed version of reprepro. [1] https://qa.debian.org/developer.php?login=brl...@debian.org#reprepro X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
