Bug#882692: libkf5coreaddons-bin-dev is wrongly marked Multi-Arch: foreign

[Helmut Grohne <helmut@subdivi.de>]

Package: libkf5coreaddons-bin-dev
Version: 5.37.0-2
Severity: important
User: helmutg@debian.org
Usertags: rebootstrap
Control: affects -1 + src:kate

libkf5coreaddons-bin-dev is wrongly marked Multi-Arch: foreign, because
it ships cmake modules on architecture-dependent paths. Thus cross
builds can fail with e.g.:

| CMake Error at /usr/lib/mips-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsConfig.cmake:48 (include):
|   include could not find load file:
|
|     /usr/lib/mips-linux-gnu/cmake/KF5CoreAddons/KF5CoreAddonsToolingTargets.cmake

libkf5coreaddons-bin-dev was installed, but the file wasn't found,
because it was installed for the "wrong" architecture.

I think the idea of the -bin-dev <-> -dev split is good. The main -dev
package is M-A:same and depends on a M-A:foreign tool package. This is
the usual layout for development packages with tools. However the cmake
files were not distributed correctly. The cmake modules should be moved
to the -dev package as their path is architecture-dependent. If you
move, don't forget to add Replaces.

Such a move leaves the -bin-dev package somewhat crippled. Accordingly,
I suggest changing its package description to say that it is an
implementation detail and that one should be installing
libkf5coreaddons-dev instead. The usual naming for such packages would
be -dev-bin so if you don't mind the round trip through NEW, I also
suggest renaming it.

In any case, the present use of Multi-Arch: foreign is wrong and breaks
stuff such as cross building src:kate. Removing it would be the quickest
solution, but likely not the final one.

Helmut