Quoting Paul Gevers (2024-01-06 13:20:11) > Thanks for being elaborate in your reply, it matches what I was thinking. (I > wasn't aware of the other examples though). there are certainly more examples. For example I maintain the package box64 which allows running amd64 binaries on arm64 but requires amd64 libc to operate. Because pkg:amd64 doesn't work for britney, I used this: Depends: libgcc-s1:amd64 | libgcc-s1-amd64-cross, libstdc++6:amd64 | libstdc++6-amd64-cross I had to patch the software to also look into the paths that libgcc-s1-amd64-cross and libstdc++6-amd64-cross use to make this work. Those two packages are Architecture:all but they do contain amd64 shared libraries. Helmut probably has a much better idea whether, in an ideal world, Arch:all packages like libgcc-s1-amd64-cross should go away and be replaced by corresponding architecture-qualified dependencies on the architecture-specific libraries. Thanks! cheers, josch
Attachment:
signature.asc
Description: signature