Thomas Schmitt, le ven. 16 sept. 2022 17:55:33 +0200, a ecrit: > Samuel Thibault wrote: > > Since AIUI the xorriso package provides only a tool whose behavior is > > exactly the same on all architectures, > > It depends on libburn which behaves different on Hurd compared to Linux.
I was more thinking about architecture (i386, amd64, arm, etc.) difference, not OS difference :) The question at stake is that when a package uses xorriso to cross-build something (e.g. an iso image or burn a CD), it's fine to use the native package for the build system, rather than sticking on the architecture of the package being built. So as to be able to build i386 images on an amd64 system or the converse, or even build arm images on an amd64 system, etc. > > could you make it > > Multi-Arch: foreign > > so that the Debian Installer can use it as foreign dependency for > > cross-builds? > > Is the described situation still suitable for Multi-Arch: foreign ? I'm not sure which situation you are referring to? > If so: Should libburn, libisofs, and libisoburn get the same change ? Libraries are sually Multi-Arch: same, meaning they have to be the same as the packages using them. That's actually already the case for libburn, libisofs, and libisoburn. Looking further: cdrskin, xorriso-tcltk, and xorriso-dd-target should probably also be Multi-Arch: foreign. Samuel