Bastian Blank: > [..] > >> What solution would make you happy here? (or at least acceptable). > > Stick to one binary package per source package. > > The only point that shows up again and again are cycles, which don't > pose a problem in the dpkg world. >
Whilst dpkg can install cycles, they only work well in special circumstances that don't apply to rust packages. For example where the same source package builds everything in the cycle, or where the source packages in question are very stable and essential e.g. glibc and gcc. The reason is when building the source package you have to install all the Build-Depends. So if source package A and B depend on each other's binary packages, and A and B are not yet in Debian, you have no easy automated way of building them. You have to do the hacky manual bootstrap way where you sudo cp stuff into /usr. Doing this for 600 rust packages, and continuing to do this in the future, is not a standard I want to adopt for the Debian Rust team, and I don't think anyone would enjoy making this part of the normal process of making rust packages. There is also the issue that rust crate often change API compatibility, so occasionally you will have to rebootstrap cycles even if one of the packages exists already in the archive but at an older version. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git
