>>>>> "Jonas" == Jonas Smedegaard <d...@jones.dk> writes:
Jonas> Yes, I am aware that the Rust team packages arch-all code as
Jonas> arch-any packages, but I am unaware that their reasoning is
Jonas> well documented anywhere. The only reason I was aware of
Jonas> when I did the switch was that Debian has a convenient
Jonas> processing of binNMUs but annoyingly require source-only
Jonas> releases for rebuilding arch-all packages.
But the bin nmu issue is a huge deal. I'm not sure for your case. But
Rust is statically linked, and so it is more likely than average to need
bin nmus. So if your packages will need to be rebuilt when their
dependencies change (I am not sure if this is true for packages just
containing crate source code), then moving from arch any to arch all
makes things significantly more difficult for SRM, RT, security team,
and people doing QA woork.
I'd definitely recommend reaching out to Adrian Bunk on this issue.
If on the other hand your packages aren't going to need to be rebuilt
when their dependencies change, it may not be a big deal.
signature.asc
Description: PGP signature
