Hi Jakub, Thanks for the feedback. If you are an expert on multi-arch support, I would really appreciate your assistance.
On 24/08/15 19:50, Jakub Wilk wrote: > Package: libm17n-dev > Version: 1.7.0-1 > Severity: important > User: multiarch-de...@lists.alioth.debian.org > Usertags: multiarch > > libm17n-dev is marked as "Multi-Arch: same", but the following file is > architecture-dependent: > > /usr/bin/m17n-config 1) My understanding was that "Multi-Arch: same" was for files that are architecture-dependent and "Multi-Arch: foreign" was for files that are architecture-independent. Is that correct? 2) Since m17n-config contains paths that include the <triplet>, should m17n-config itself be placed somewhere architecture specific instead of in /usr/bin/ ? Are there some good examples of packages that are multi-arch enabled that deal with the same issue? 3) re: https://wiki.debian.org/Multiarch/Implementation: ---------------------------------- /usr/lib -> /usr/lib/<triplet> /usr/lib/<pkgdir> -> /usr/lib/<triplet>/<pkgdir> /usr/include: no change /usr/bin: no change /usr/share: no change /usr/sbin: no change ---------------------------------- What should happen to files in /usr/lib/debug/? Should they reside in /usr/lib/<triplet>/debug/ ? Thanks, #
