* Johannes Schauer <jo...@debian.org>, 2016-02-10, 11:09:
I am a maintainer of chasen package. It contains chasen-config, it
work as pkg-config like but it's a single script.
Latest lintain reports:
E: libchasen-dev: old-style-config-script-multiarch-path usr/bin/chasen-config
full text contains architecture specific dir x86_64-linux-gnu
But I want to keep libchasen-dev as Multi-Arch: same. Would you tell
me finding the correct way to change the script?
[...]
The old-style-config-script tag which src:chasen suffers from as well
and which was also linked to by Bastien contains more valuable
information. The important message is: please use pkg-config and not
some package-specific configuration mechanism (as also already pointed
out by Vincent). Otherwise, you (and/or upstream) will suffer from an
unnecessary maintenance burden in case you ever want to (or in case we
need to) cross-build that source package. For now though it should be
sufficient to move the file into an architecture specific path.
Um, no. Replacing an upstream-supported API, which has existing users
even in the Debian archive, with a Debian-specific non-upstreamable one
sounds like a very bad plan to me.
--
Jakub Wilk